You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the memory usage as shown in the overview page is not comparable to other languages.
The bash script fork to different processes many times by piping outputs to other binaries. I think the memory usage of those separate processes is not accounted for.
The text was updated successfully, but these errors were encountered:
Perhaps, but the larger problem there is that the sort command is actually implemented using an external sort (partitioning the data and sorting in temp files) rather than a fully in-memory sort as with all other implementations. This enables it to run on very large data sets with minimal memory use (just an index), but makes it extremely slow in comparison and highly dependent on I/O performance.
All other operations in that pipeline can operate on a line at a time with minimal memory use.
I've got a PR in WIP state that partially addresses this by using the -S 40% option to specify a percentage of physical memory to use in buffering data for sorting - #75
I think the memory usage as shown in the overview page is not comparable to other languages.
The bash script fork to different processes many times by piping outputs to other binaries. I think the memory usage of those separate processes is not accounted for.
The text was updated successfully, but these errors were encountered: