3 ms·
One consideration might be which Lisp you're using. SBCL is known for its speed compared to other CL implementations, for example, so using it (especially now
by yellowapple 10y ago
One consideration might be which Lisp you're using. SBCL is known for its speed compared to other CL implementations, for example, so using it (especially now that it's the one recommended Lisp to use with StumpWM) might help considerably.
I personally don't notice any significant performance issues, even on old single-core 32-bit hardware.
- girzel 10y agoI was using SBCL! Here's an old mailing list thread about it. It often took StumpWM a second or two to notice that I'd typed the prefix key. https://lists.nongnu.org/archive/html/stumpwm-devel/2014-03/msg00043.html https://lists.nongnu.org/archive/html/stumpwm-devel/2014-03/...
- lokedhs 10y agoWhile I have no idea what caused your problems at the time, I can assure you that it's nothing like that today. There is zero delay anywhere in it, and it's as fast it can be (in other words, I don't know of anything in it that, if made faster, would even be noticeable)
- yellowapple 10y agoCome to think of it, I recall some performance issues that supposedly existed if SBCL was compiled with threading support. It's since been resolved, though, as far as I can tell.
- lispm 10y agoMany Lisp implementations are in the speed range of SBCL. When you look at such an application, the super optimized part of the code is not that large. Equally, if not more, important is the robustness of the runtime system against all kinds of errors, the speed and responsiveness of the memory management system and the speed of compiled code which runs with full safety checks. Also if a Lisp system would use much of CLOS, the speed of the CLOS implementation and the library one writes with CLOS becomes important. If there are speed problems in an application like Stumpwm with the current Lisp systems, it is definitely not the raw micro-bench speed that's a problem, but more likely something else (architecture, threading, GC, event handling, bugs, ...).