See here
http://en.wikipedia.org/wiki/Program_optimization#Quotes
Rather do some actual measurements before changing code.
On 2012-02-13 14:05, Wolfgang Pedot wrote:
Hi,
Sorry this isn't answering your question... but I've worked on a project
with thousands of threads and found it to not actually really cause any
issues (Except for hitting the thread limit for a process). Does the
large number of threads cause issues for you? I guess for large
scalability you could improve the number of open databases by 3 times,
but I would have thought at that scale you would hit memory issues?
the number of threads does not cause issues (yet), its more like an
optimisation.
If we had issues I would definetly make the time to look into the code
right now ;)
This has been in my head for quite some time, I just dont like the
idea of having tons of idle threads floating arround.
You could also close idle databases dynamically (If over a threshold)?
And put a limit on the number of databases to open at a time? That
should help with memory usage too...
Just thinking, models for handling threads really interest me :).
Limiting the number of open databases is a last resort because that
would mean limiting functionality for some users.
There is an "idle"-timeout for the databases but it does not hit often
because there is always some activity.
thanks for your input
Wolfgang
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
