This could be another optimization, but that wont help if I have a table 
with millions of rows and an assumed column width of 4MB of data.
With 4 GB heap, any value of MAX_MEMORY_ROWS > 1000 will lead to OOM Error 
when selecting from that table.
And a value of 1000 might not be high enough for index creation, if there 
are millions of records.
So both won't be possible for the same session.





From:   Noel Grandin <[email protected]>
To:     [email protected]
Date:   21.05.2019 18:08
Subject:        Re: [h2] OutOfMemory when creating an Index
Sent by:        [email protected]




If you are trying to prevent users from exceeding memory resources, your 
best bet is just to use a connection pool and limit the max number of 
connections. 
Note that even if a user issues multiple queries in parallel to the same 
connection, those queries will execute sequentially server-side.

I still maintain that your existing performance will be terrible compared 
to what it could be, since you are effectively limited by very slow disk 
IO, even for very small queries.

If you limit the max number of connections, and raise MAX_MEMORY_ROWS to a 
reasonable number, you will experience a net gain in performance.
-- 
You received this message because you are subscribed to the Google Groups 
"H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/CAFYHVnXte%2BOQMcFj6A1RqKXasXdoDFrHhdDaavry4U4qkSk%2B6g%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.


================================================================================================================
Disclaimer
The information contained in this e - mail and any attachments ( together 
the "message") is intended for the addressee only and 
may contain confidential and/or privileged information. If you have 
received the message by mistake please delete it and notify 
the sender and do not copy or distribute it or disclose its contents to 
anyone.

FINARIS Financial Software Partner GmbH, Sömmerringstr. 23, 60322 
Frankfurt/Main, Germany
Registered at Frankfurt/Main, HRB 52873, Managing Directors: Dipl. Inf. 
Hermann Friebel, Dipl. Ing. Kai Bächle, Dipl. Inf. Werner Märkl
================================================================================================================

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/OFCC6B4677.78567CAC-ONC1258402.00341A4E-C1258402.0034DFB7%40finaris.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to