Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
@Friedhelm!
This isn't the main point! You have to configure it and it is different per platform. Creating a file always has an overhead and it needs cleanup. The functionality has been implemented at a time where we had not much memory available. I would also not fully trust those type of function in Windows! The file caching isn't implemented in the way I would expect it. Domino had to add work-arounds to avoid Windows memory management issues before!
Also Domino is cross platform and this would be a cross platform solution. On Linux you have tempfs but I still this needs to be configured. And also keeping track of temp files, creating them and removing them is overhead not needed.
A simple memory allocation with a fall-back to the old method would be much easier.
-- Daniel
+1
I think on Windows this is not necessary as long as the temp file is created properly with the right flags set:
For more information, see the Caching Behavior section of this topic.
This causes Windows to keep changes to the file as long as possible in Cache, postponoing any writes as long as possible. This is more flexible than using RAM only.
I however suspect current Domino does not use the right attribute settings for view rebuils.
Regards, Friedhelm Klein, Axians IT Solutions
In 2010 we dramatically improved performance of our Domino servers on Linux by moving view rebuild operations to RAM disk.