 2 | computers today have at least 2GB RAM, I don't think that running the Doctor with 512MB max heap ... ticket with link to this database. I just checked the 64MB sample database. With 512MB max heap ... the database and additional 20 seconds to rebuild a new database. With 256MB max heap size I got the same |
2 | working. 2) * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at MAX * Batch ended at '2LG ... ended at MAX If MAX is the last, then it looks like that every thing is ok. 3) An Exception |
2 | where do i put the max="100" /> max=100" ; test[1 ... server command or argument: connection port=6136 max=100 (error 531) Am not sure this is the right |
2 | " />
max="8mb" stdout="true" stderr="false ... ="256kb" page="2kb" />
max="128mb ... " />
max-threads="10 |
2 | questions regarding the configuration entry:
...
max-threads="10" synchronized="false" /> ... max-threads we have 16 processor cores and around 400 clients communicating ... could be around max-threads="16", but there are no strict rules and tuning for a specific application requires |
2 | these settings: Page Cache max-threads="10" /> Query Cache: max-threads="10" /> > Query Cache: max-threads |
1 | There seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX ... ) correctly return "ThinkMachine MAX SX 20". Regards. Thank you for this report. Please try build 2.6.5 |
1 | ="true" sync="false" path="." max="128mb" />
max-threads="10 |
1 | cache="64mb" max-threads="10" /> The problem occurs ... " max-threads="10" synchronized="true" /> When synchronized is enabled, all operations |
1 | max="100" /> The element specifies how clients can connect ... the JPA Overview section in chapter 3). The max attribute specifies the maximum number |
