|Optimizing Save Times|
|Sometimes saves take a very long time. Why?||
Virtual Memory (VM) is probably on. Helix has its own VM scheme and when Apple's VM is on, the two sometimes get into a 'discussion' that can last an hour or more.
If you are patient, Helix will eventually finish the save. The best option is to disable VM, but if you need to leave VM on, modifying the HDTM resource in Helix may alleviate the problem. Contact technical support if you plan to attempt this change, but remember: we do not recommend using VM on a Helix Server.
|What is the best setting for the Finder's disk cache?||Informal testing has shown that setting the Finder's disk cache above 1024K results in decreased Helix performance. Setting the Finder's disk cache down this low will have a detrimental effect on Finder performance, so if the computer in question is also used for other tasks, you may want to experiment to determine the proper balance for your situation.|
|Why does my Helix shut down after a short time?||
You are most likely running a demo version of Helix. Make sure the key you enter is not a demo key. See this technote for more information.
|Does AutoSave really help reduce crashes?||
Yes. AutoSave allows Helix to commit changes to the collection to the disk instead of trying to maintain them in memory. If a low memory situation occurs, AutoSave will force a save and memory can be freed up.
|In the AutoSave dialog there is a checkbox labelled "Save and clear caches." Should this be on?||
In general, no. Unless you have been instructed by Helix technical support or your developer to turn it on, you are probably losing server performance and gaining nothing. Save and clear caches was added some time ago when certain sites were experiencing an odd data caching situation that caused the server to slow down significantly the longer it ran. Turning this on eliminated the problem by forcing Helix to empty its caches every time a save occurred. The downside to this is that the server will rarely be able to take advantage of cached information and will have to go to the (slower) hard disk to find data more often.
|What is Save & Log?||
With Save & Log turned on, Helix maintains a seperate logfile of all data entries. If Helix crashes, the logfile contains all of the data that was entered since the last save occurred. When you restart Helix, it will read the data entries from the logfile and apply them to the collection. Note that there is no option to 'save and log' work done in full mode.
|Why doesn't Helix just save the data to disk immediately like FileMaker does?||
All good applications should offer a "Revert to Saved" option. By saving immediately, you have no option to revert should you discover that the information you just entered is wrong or that the operation you performed (i.e: delete all) was not what you intended. Helix's Save and Log gives you both security and flexibility not offered by other packages.