poolcraft / shimeji-ee

Automatically exported from code.google.com/p/shimeji-ee
0 stars 0 forks source link

Better memory usage #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Shimeji uses a lot of memory and may have a memory leak.  This should really be 
investigated.

One way to improve the memory usage would be load each image once and keep 
references to them.  Shimeji currently loads a new image for every action in 
the actions.xml, which is excessive because images are often reused.  Each 
Shimeji requires about 5MB with the standard configuration files when it really 
only needs one or so.

Original issue reported on code.google.com by relic...@gmail.com on 6 Nov 2010 at 8:38

GoogleCodeExporter commented 8 years ago
Each Shimeji type requires a lot of memory.  With some careful managing, the 
memory required can probably be halved.

Original comment by relic...@gmail.com on 10 Nov 2010 at 3:13

GoogleCodeExporter commented 8 years ago
Dear Project Members, please kindly tell what "careful managing" can be used to 
decrease memory usage. I've cut the duplication possibility already, but still 
some small memory leak exists.

Original comment by ketrincr...@gmail.com on 11 Nov 2014 at 11:13