Incriminated wrote:And i have another little question: When PrimoCache starts it searches for updates. Is this actually working in the beta-stadium or is it just for later use. Will I get i.e. 0.9.1 automatically, or do I have to scan the forum-threads?
Automatic update check works in the beta version.
Incriminated wrote:I think the option "Release After Write" and "Overcome HDD C1 Issue" did make a serious difference in performance in fancycache versions depending on the scenario.
Well, "Overcome HDD C1 Issue" is not designed to improve the performance. Regarding with "Release After Write", did you really see the great performance boost with this option?
Let's say i have 2GiB R/W-cache. Then I write 1GiB on that disk. With Release after Write after that this amount is beeing freed instantly. Now lets say i want to write a second file that also has 1GiB. This would mean when release after write is not enabled that it keeps the first 1GiB in cache and free's the data that is stored in the read-cache to make place for the second 1GiB write. So when i next try to open a file that was cached before, it needs to be read from disk once again.
This is hard to measure, but i definetly think what I assume by that is correct and that "Release after write" can have a serious impact dpenending on strategy and cache-size. Correct me when Im wrong.
And please tell me why you not want me - as an advanced user - to be free to choose to enable/disable such things by my own... i already heard that you want to simplify, i have no prblem with an optional simple/advanced settings-structure. But one other way would be to simply provide a meaningful manual and not some wish-wash like here: http://www.romexsoftware.com/en-us/fanc ... /help.html
<- Nothing here is of help, not a single option is properly explained so I get a meaning of what to choose. i.e LFU/LRU ... it is of practically interest what to choose in which scenerio for benefit, not what it technically does and force the costumer to study IT to get an idea of what he wants in his particular use-case! An easy explanation is more worth than a simplification without a note.
Counterwise I would like to ask you, as the support/developers: Did you NOT see any great performance boost from this feature.
In the end, i don't know if the files I write now get released after write or if they will be kept until all read-cache is flushed and cache is full.
Last thing is totally not improving my performance because i nearly NEVER access the files i just write right after.
I want to use lowest possible amount of the L1 to be used for write... so NOT to flush out any read-data if avoidable.
I simply do want to tell the program to "Release (the data) after write".
Whats wrong with my demand?
PS: Im sry that i have to correct you with your own "help-file". Overcome HDD C1 Issue: C1
value on some mechanical hard disks, especially laptop disks, may increase quickly when Defer-Write is enabled. This option is designed to avoid such issue. SSD users can disable this option for better performance.
-> So obviously YES this option is described/designed to improve performance on SSD, so Im asking why it is removed and how PrimoCache now make sure SSD doesn't run into performance problems while this option is gone without a note.
You should try to inform your costumers about the functions of your programm instead of start simplifying at all cost.
I personally think even more possibilities for advanced settings are welcome. This programm beeing complex is natural, and I very much respect it and would buy it especially because it is highly configurable. Still there's no problem with a simplyified "cache-setup-assistent" or other way around "advanced-options-tab". Making it suitable for both - simple and advanced users - is not - I repeat: IS NOT - in opposition to each other.