 1 | Hi, I'm running objectdb in server mode, config as it comes out of the box. In this case the database is being used as a queue with multiple seperate processes, each with multiple threads, writing messages. The message is split into a lightweight metadata message to allow fast searching |
1 | for your fast response. You were right, I forgot about this schema change. Glad you found it... Thanks Markus Ritter Good. Thank you for the update. doppelrittberger |
1 | constructor so now getting pm is very fast even having 300 PC classes. In the future |
1 | and thought for some reason it didn't get posted. (Didn't expect such a fast response either.) I |
1 | too. But when i retrieve objects from my local DB it was too fast where as it is taking so much time |
1 | the file for example in %TEMP% Please try build 2.7.0_04. Thank you very much for the fast fix. We had directly used the new version. btc_es |
1 | and another dedicated disk only for the recovery file. Using fast SSD disks. Once in a while the recovery |
1 | have change this and cut heap size to 512MB, so database should crash much faster. That was fast |
1 | will probably be very fast. If you need to query the data in the database with the pending changes in |
1 | . However, the last build of ObjectDB seems to run this query fast, so it is possible that this issue has already been fixed. Could you please check build 2.8.0_04? btc_es |