Vlad Ilyushchenko

We have memory telemetry in the latest (6.0.6) release. It would be useful to obtain that if that’s the version you are using

Thanks a lot for this information. Could we drill down into data loss please? Could you post errors from questdb log? Grep for ‘ E ‘

How do you run questdb? Docker or binary?

Could we have full log from fail run ? We also need context around the error log lines to understand what the issue could be

there is PR in ready to go to tackle high memory consumption: https://github.com/questdb/questdb/pull/1373

thanks, I've seen this `String is outside of file boundary` elsewhere too. Is this new set of tables you're inserting to or have they been upgraded from previous QuestDB version...

We added configuration parameters for cases when there is large number of small tables, please see #1369

is this still ongoing?

configuration related test failed: ``` 2022-10-19T17:18:28.656458Z E i.q.TestListener ***** Test Failed *****io.questdb.PropServerConfigurationTest.testImportWorkRootCantBeTheSameAsOtherInstanceDirectories2 : org.junit.AssumptionViolatedException: got: , expected: is at org.junit.Assume.assumeThat(Assume.java:106) at org.junit.Assume.assumeTrue(Assume.java:50) at io.questdb.PropServerConfigurationTest.testImportWorkRootCantBeTheSameAsOtherInstanceDirectories2(PropServerConfigurationTest.java:1093) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at...

my bad, junit timed out on the network somewhere