One thing I noticed regarding manifold which might benefit from some work is it allocates quite a lot and creates deep call stacks even for "trivial" code.

Any scenarios in particular you think should be looked into @UK0810AQ2?

I think we noticed that too in our code ... (not 100% sure it's manifold). I remember lots of threads and thread exhaustion by manifold threads. I checked to see if we can limit the pool but did not find things. (new to clojure)

@eugen.stan If you have a memory snapshot you can share, that would be awesome. If you were returning InputStreams of any sort in Aleph, I might have a fix for the memory leak here: https://github.com/clj-commons/aleph/issues/523#issuecomment-1075429913

@U10EC98F5 I forgot I already had profiling results for a server with Aleph and manifold, you can take a look at the flame graph and see where time is spent https://github.com/bsless/stress-server/blob/master/results/svg/aleph.ring-middleware.async.java15.G1GC.svg

raw view is more convenient https://raw.githubusercontent.com/bsless/stress-server/master/results/svg/aleph.ring-middleware.async.java15.G1GC.svg

@UK0810AQ2 thanks for sharing that. The SVG isn't labeled in the deep call stack (on my phone), but can I generate a new one from the repo? I'd like to zoom in if possible. My immediate guess is work is being done on the main thread that should be on an executor thread, but I'll have to see

@U10EC98F5 entirely possible, feel free to dm me and we'll schedule something