armedbear-devel

Download

armedbear-devel@common-lisp.net

November 2018

3 participants
2 discussions

Re: ABCL efficiency and build settings
by Mark Evenson 27 Nov '18

27 Nov '18

> On Nov 22, 2018, at 06:54, ThutmoseIII Thoth <thutmosethree(a)gmail.com> wrote: […] > How well do these debugging/profiling facilities work with ABCL? Will I be able to find out the name of lisp functions being called during a profile or only Java functions? CCL has this problem where we cannot get the lisp functions names in profiling, only the objective C methods. The inspectability of the JVM call stack is certainly better than Clojure even from just reading the function names. Using a [customized version of SLIME][1] allows the use the [ABCL-INTROSPECT][2], which is probably the most advanced way of debugging ABCL. [1]: https://github.com/easye/slime/tree/evenson-20170914a [2]:https://gitlab.common-lisp.net/abcl/abcl/tree/master/contrib/abcl-intros… As for your suspecting that your application is spawning more threads than you would expect, from your code snippet I can’t really offer much other than to wonder what the definition on the DISCONNECT involves. Again providing an example of code, even a stripped down toy application that demonstrates the problem would be enoromously more useful for me to help out. — -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 2

ABCL efficiency and build settings
by ThutmoseIII Thoth 15 Nov '18

15 Nov '18

Greetings ABCL developers! I have built an application with ABCL and am very pleased with both ABCL and my application, but I would like some help and suggestions in terms of the efficiency of my program, building settings, and perhaps JVM tuning. In the OS X Activity Monitor, my application is reporting to be using 29 threads and 200% of the CPU — This is enough to make my computer HOT to the touch! The equivalent program was running with CCL and cocoa at about 70% CPU and about 10 threads and was not hot to the touch… My program is fairly simple in that it just displays images in a JFrame that it gets from bytes over a socket. For this program I decided to handle each socket and display on its own thread, so I’ve only created two additional threads. I “built” the program by compiling all the .lisp files into .abcl files, then writing a tiny Java main function which creates an Interpreter and loads each .abcl file and finally calls Interpreter.eval on a lisp function which starts the program. I am using the Oracle Java 1.8 Hotspot JVM and ABCL 1.5.0 built from source. Thank you and please write back with suggestions and questions that will help me make my program run more efficiently.

2 1