Dump the Trash.
- In Eclipse, click Windows --> Preferences --> General --> Show Heap Status. Then click OK. At the bottom of the window frame, you will see the memory being used in the window (dynamically changing), then the total memory allocated next to that, then a little trash can. Composer can clean up its own memory a little bit when you click on the trash can to dump unused memory allocation.
Reboot your computer, THEN generate code.
- In earlier versions of Composer (8.1.3.xxx) I also experienced a memory leak, where the used memory slowly grew after hours of development work until it was occupying more than 1 gig of RAM. After a reboot, it would initiate at closer to 400 meg.
Increase your RAM.
- Since 2013, I have never used Composer with less than 8 gig and never had a speed problem with 16 gig of RAM.
Increase your processing power.
- You will see your best performance on a dedicated virtual server, where you can get away with 4 gig of ram, but you are burning dual Xeon Gold 6150 processors at 2.7 ghz. (wide grin).
Happy Coding!
------------------------------
Todd McCall
Bank of America
------------------------------
Original Message:
Sent: 02-20-2020 05:33
From: Omar Elhawary
Subject: Composer performance
make new work space or delete the .metadata from your works pace, but please note that this is same as making new work space.
------------------------------
Omar Elhawary
Original Message:
Sent: 03-08-2016 11:47
From: Alfonso Villafranca
Subject: Composer performance
What can i do to improve composer performance?
When i generate callflows codes the delay is about 20 minutes, my callflow is large but how can i improve the performance?
I have a Core I5 processor 2.6 GHz, 4 GB RAM
Thanks