I would rather try to add RETENTION_TIME=0 On Tuesday, June 21, 2022 at 8:28:42 AM UTC-4 Ulrich wrote:
> My URL parameters are: > LOCK_TIMEOUT=86400000;WRITE_DELAY=10000;MAX_MEMORY_ROWS=1000000;MAX_OPERATION_MEMORY=50000000;ANALYZE_AUTO=0 > > I'll check if the compact algorithm works (better) with the default > parameters. > > [email protected] schrieb am Donnerstag, 16. Juni 2022 um 03:31:05 > UTC+2: > >> I wonder how your url looks like, what parameters you are using, >> specificaly RETENTION_TIME and WRITE_DELAY ? >> Are any LOBs involved? >> With default settings auto compaction should take place in the >> background. Whether or not it can keep up with the rate of updates, is a >> different story, but the fact that idle database is not compacted at all is >> worrysome. >> BTW, the fact that file is not shrinking does not nesseccarily means that >> there is no compaction going on, like the fact that JVM heap is not >> shrinking is not an indication of GC absence. >> On Tuesday, June 14, 2022 at 5:04:26 AM UTC-4 >> [email protected] wrote: >> >>> >>> >>> On Tue, 2022-06-14 at 08:11 +0200, Noel Grandin wrote: >>> >>> In general, compacting should work while the db is running, but it's >>> fairly conservative >>> >>> >>> Noel, >>> >>> not arguing, you know that we do love H2 and are grateful. >>> Although I never saw any online defragmention doing anything. >>> >>> We have 300 MB defragmented content blown up to 20 GByte. The databases >>> are idle during the night and most time the day. >>> Heavy Delete/Write/Querying happens only in the early morning -- but it >>> never shrinks, only grows, until "SHUTDOWN DEFRAG". >>> >>> Best regards >>> Andreas >>> >>> >>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/c23ccd12-5e92-4479-844c-bf9a1e7618f0n%40googlegroups.com.
