Open wenzowski opened 8 years ago
Here's a full diff of https://backside.dialogue-map.wenzowski.com vs this repo.
When you start doing serious topic mapping with it, the database (ElasticSearch) infrastructure maintains a couple of really large LIFOs. Those can get huge when proxies get fat. Certainly don't need that for testing; my settings reflect large data importing and manipulation.
Perhaps we could comment on resource requirements in the Readme then? Is there any way to reduce the likelihood of hitting an OutOfMemoryError with those LIFO queues?
requires instrumenting; that has not been on the table (yet)
Does BacksideServletKS really need a 4GB heap with a 1GB initial allocation? I've just deployed this with
java -Xms32M -Xmx256M
.