PokIsemaine commented on issue #2284: URL: https://github.com/apache/kvrocks/issues/2284#issuecomment-2158006313
Hello @AntiTopQuark, I am also interested in this issue. When I implemented the Sort command before, there was a need for memory restrictions. ``` /// SORT_LENGTH_LIMIT limits the number of elements to be sorted /// to avoid using too much memory and causing system crashes. /// TODO: Expect to expand or eliminate SORT_LENGTH_LIMIT /// through better mechanisms such as memory restriction logic. constexpr uint64_t SORT_LENGTH_LIMIT = 512; ``` It seems that the current memory statistics of kvrocks are still coarse-grained process-level statistics. Do we need more fine-grained tracking statistics? I've collected some references: https://cwiki.apache.org/confluence/display/DORIS/DSIP-002%3A+Refactor+memory+tracker+on+BE https://doris.apache.org/blog/Say-Goodbye-to-OOM-Crashes/ https://www.modb.pro/db/1798912145290776576 They seem to utilize the memory allocator to achieve this, would you like to share and discuss your thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
