actually, a smaller demo would be something that creates a proxy, runs a method on the proxy that does proxy super, and while the super method is running, does an update-proxy, when the super method return and the call to proxy-super completed it would clobber any changes made via update-proxy

I vaguely remember a bug related to this, but it wasn’t with proxy-super - I believe it was when proxying a class whose super constructor calls a method on the object - that method is not initialised at that time.

I'm trying to debug code that is spending about 25% of the time sitting in: clojure.core$promise$reify__7005.deref(). Any suggestions?

(At least according to Visual VM sampling.)

This is Clojure 1.8.0

isn't derefing a promise expected to block until the promise is delivered?

i.e. are you sure you're not spending 25% of your time waiting for the promise to be delivered?

I have a thread-local atom I use reset! to preserve state. When I comment out the reset! line it speeds up. Even if I reset! to a constant it's slow.

Any ideas on how to find which deref is the performance issue?

Hm...I'm seeing hundreds of async-thread-macro-### threads.

#clojure-dev is for discussion about development of clojure itself, for help with your clojure programs #clojure is a good place to start

Sorry about that.