Gwyneth wrote:
What version are you using, Ai? I have seen a fluctuation of viewer-side FPS on an apparently 'empty' region, usually a signal that there is some 'invisible' back-end processing at the simulator level, but haven't been able to track it down to anything yet. Selecting a lot of prims and linking them together now takes quite a lot of time (sometimes even a minute or so!). This is on 0.8.0 Dev 722f030. I suspected some delays while writing to the database, and having some sort of database journal being written to a lot of times would certainly account for that!
I was using the OSGrid latest add-on region release from a few days ago (r/24670) Gwyneth.
Dahlia wrote:
Translate scene should complete quite quickly, all it does is move the objects in the scene. What you are probably seeing is the changes being saved to the database, an entirely different process. If you are using Sqlite for your region database than storing changes to the scene will always be quite slow. It would likely take just as long for loading an oar with the same number of objects and saving them to the database. If you need faster region storage, try using one of the other database options such as mysql.#
That's right Dahlia. The translate scene on 600 or so objects was essentially instant and I was able to move the avatar about (using ODE temporarily until Robert's r/24672 commit is in the OSGrid release) in the new negative Z underwater area fine. It was indeed as I did the shutdown... and I did assume it was the persisting to data base part.. that took nearly 30 minutes. It was SQLite for the add on regions we have for experiments.. not our MySQL usual data base. But still.. constantly creating and deleting the db-journal file (perhaps once per DB write?) MUST make this persisting process slower than needed? I also thought I better make sure the persisting process completed even though it as taking ages or else there may have been only a partial translation. If I had not had the opensim\bin window open I would have thought the OpenSim.exe console was jammed and stopped wit with the X on the console window... I assume that would NOT have been good, so it could be a source fo problems if persisting objects takes so long. A better indication of progress might be to put a dot out every 50 or 100 objects persisted on the console to remind the user the region OpenSim.exe still need time to complete.
_______________________________________________ Opensim-users mailing list [email protected] http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
