Opened 13 years ago
Closed 12 years ago
#180 closed defect (worksforme)
Stack overflow memory conditions with lparallel
| Reported by: | Mark Evenson | Owned by: | Mark Evenson |
|---|---|---|---|
| Priority: | major | Milestone: | 1.1.0 |
| Component: | other | Version: | 1.0 |
| Keywords: | lparallel stack-overflow jvm multi-threaded | Cc: | |
| Parent Tickets: |
Description
With the 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.
Change History (2)
comment:1 Changed 13 years ago by
| Summary: | stack overflow with lparallel → Stack overflow memory conditions with lparallel |
|---|
comment:2 Changed 12 years ago by
| Milestone: | unscheduled → 1.1.0 |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Still valid?
Note: See
TracTickets for help on using
tickets.
"maximize the actual usage of the available […]"