![]() |
#1
|
|||
|
|||
"Minimizing updates to the database" FAQ
Is the FAQ "Minimizing updates to the database (single-user mode)" up-to-date and valid for URp 4.x on Windows 7 x64?
I downloaded multiusermode.zip, closed UR, ran (merged) DisableMultiUserMode.reg and confirmed existance of the key/value using Regedit. Next, I started UR, looked for Tools | Options | Miscellaneous, Delay, but there is no Delay option (at least not in URp 4.2). Finally, I set "Tools | Options | Editor | Auto-save changes every x minutes" to 15. Despite these actions and even closing/starting UR a second time, the database is still being updated every 60 seconds when open and not in use. FAQ: http://www.kinook.com/Forum/showthre...+AND+multiuser |
#2
|
|||
|
|||
Re: "Minimizing updates to the database" FAQ
Quote:
Quote:
Quote:
|
#3
|
|||
|
|||
Thanks for the quick assistance and 4.2.0.5 update. I should explain why I'm using this FAQ.
I keep seperate UR databases for home and work. The remote database is only there for reference/backup purposes. I keep the home and work UR folders synced with online storage and with each other (currently using Windows Live Mesh). (BTW, this is why I wish UR had an internal per-database read-only option instead of having to change the file itself to R/O--which would be problematic in this 2-way sync scenario.) Anyway, with SingleUserMode already enabled, I installed 4.2.0.5, rebooted, started UR, and tried everything from leaving "Delay before updating item access date" at the default 4000 milliseconds to setting this and auto-save changes to 0 (and restarting). Live Mesh continues to re-sync every 10 seconds as long as an UR database is open. Before I made all these changes I observed re-sync approx. every 30 seconds, so it's actually getting worse! The modified datetime is not changing, so I don't know what is making Live Mesh, Sugar Sync, etc. go crazy when it comes to UR. |
#4
|
|||
|
|||
I don't see any reason why sync apps would think the .urd file has changed when open in UR if single-user mode is enabled, but we'll add to our list to do some testing w/ Live Mesh, and also consider providing a way to open the database read-only even if the file itself is writeable.
|
#5
|
|||
|
|||
Thank you. I'm gonna throw Process Explorer at it this weekend and see if I find anything useful.
|
#6
|
|||
|
|||
I'm no expert at using Process Explorer, but I can see recurring I/O activity in the Read and Other section. No activity in the Write section after initial startup. (See screenshot. The second monitor window was captured a minute or two after the first.)
A very tiny amount of data is involved each time--16 bytes in this case. I've seen up to 48 bytes in PE views of Live Mesh. Yes, it triggers sync approx. every 10-30 seconds, but perhaps this isn't enough data to be worth bothering with? Whatever you decide, I hope we can at least have UR read-only database mode at some point. There are many cases where I'd like to open a databases read-only to avoid accidental updates (without having to change the file attribute) and have one or more open in normal read/write mode at the same time. ---------------------------------------------- P.S. I noticed my last post was #100 which finally clicked me over to "Senior Member" after all these years. I don't know whether to expect balloons and party whistles or a walker with a big white bow on it, LOL! Last edited by mikeg; 11-24-2010 at 03:02 PM. |
#7
|
|||
|
|||
After living with this issue for several months, I would say adding capability to open an UR database in virtual read-only mode while the underlying file is writable is definitely more important than figuring out how to stop what turned out to be tiny amounts of data (probably polling) when syncing files with Windows Live Mesh.
My scheme with home, work and laptop (travel) UR databases sync'ed up to all three locations works fine as long as I don't open the two "remote" files. The moment I open a remote DB in UR I get a location_(computerName).urd shadow copy synced to all 3 locations which quickly becomes a mess. Hope you can fit "open and search DB's in virtual read-only mode" somewhere in the already packed road-map. ![]() |
![]() |
|
|