#180: stack overflow with lparallel ---------------------------------------------------------+------------------ Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: unscheduled Component: other | Version: 1.0 Keywords: lparallel stack-overflow jvm multi-threaded | ---------------------------------------------------------+------------------ With the [http://lparallel.com very interesting lparallel library], ABCL can get into some stack overflow situations (especially on newer JVM implementations).
Also, I get the feeling that the BORDEAUX-THREADS mapping for ABCL is not optimal, as when I run LPARALLEL full out on a many worker kernel, I don't maximize the actual available CPU/RAM on a multicore x64 system.
#180: Stack overflow memory conditions with lparallel ---------------------------------------------------------+------------------ Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: unscheduled Component: other | Version: 1.0 Keywords: lparallel stack-overflow jvm multi-threaded | ---------------------------------------------------------+------------------
Comment(by mevenson):
"maximize the actual usage of the available […]"
#180: Stack overflow memory conditions with lparallel -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: closed Priority: major | Milestone: 1.1.0 Component: other | Version: 1.0 Resolution: worksforme | Keywords: lparallel stack-overflow jvm multi-threaded -------------------------+-------------------------------------------------- Changes (by mevenson):
* status: new => closed * resolution: => worksforme * milestone: unscheduled => 1.1.0
Comment:
Still valid?
armedbear-ticket@common-lisp.net