Knowledge Base > ELC > Optimizing ELC Performance: Usage Reporting and Memory

Need Support?

Can't find the answer you're looking for? We're here to help.

Optimizing ELC Performance: Usage Reporting and Memory

Overview

Users may experience sluggishness in the ELC console or find that historical usage reports fail  to generate. This typically occurs when the default memory allocation is insufficient for the  volume of licenses being managed or when the reporting database has grown significantly.  This guide will help you in updating your ELC settings. 

Reports in ELC 5.5 are highly customizable. By accessing the Reports section (or  reportsData.jsf), administrators can filter by user groups and date ranges. Increasing the Java  Heap size ensures that these modifications and data-heavy exports do not time out or crash  the License Center service. The default JVM heap size for ELC 5.5 is often set to lower than  512MB, which is insufficient for environments with hundreds of concurrent users or years of  historical reporting data.  

You must make sure you first have a Minimum 1 GB RAM and Minimum 100 MB hard disk  space for the installation of ELC server. This should be increase if you want to run reoccurring  reports daily or monthly.

Optimize Reporting

  • Schedule Report Task Manager: this section will show you the schedule report next date.  When you run scheduled reports, ELC has to pull data from the database, hold it in “active  memory” to format it (into PDF or CSV), and then output the file. Often check the scheduled  and remove any older reports no longer needed to clear memory.In the ELC Console, navigate to Reports 
  • Run reports in smaller increments (e.g., monthly vs. yearly) This will reduce memory overhead.
  • Format: You can choose between viewing the data in the browser, exporting it to CSV (for  Excel), or generating a PDF. 
  • Automation: Once you have “modified” the report parameters to your liking, you can click  Schedule Report to save those specific settings into the Scheduled Report Task Manager. 
    http://localhost:5580/admin/reportsData.jsf 

Troubleshooting ELC Reporting using the Logs

Enabling Debug logs:

First add the following to the  elise.properties file to enable debug Logs and restart ELC: 

debugReportLogs = true 

If errors appear in the db.log file (located in the $ELC_HOME\logs directory), please open up a Support ticket and provide the following:

  •  The db.log file 
  •  JDK version you are using 
  •  OS you are running ELC on
  •  A description of the error(s) you are seeing 

Java Heap Size errors:

Additionally, larger report queries force the JVM to load massive datasets into memory, leading to a “Heap  Space” crash. The symptoms are:

  •  The ELC web interface is slow to respond or times out. 
  •  “Out of Memory” or “Java Heap Space” errors appear or time out 
  •  Reports fail to generate or return empty results for long time-spans. 

Steps to Fix the Issue 

ELC checks for the JVM and System Status based on your machine and the size of OS This is  found in the License Server Status Page 

http://localhost:5580/admin/server_status.jsf 

Stop the ELC Service: Ensure the Embarcadero License Center service is fully stopped before  making configuration changes. You can get your IT to increase your Heap Size of your machine  and reinstall ELC. 

You may try an alternative method to Increase Java Heap Size (JVM) 

Navigate to C:\Embarcadero\ELC5.5\LicenseCenter\bin\  and look for elise.properties – Right click into notepad  This is for applications running on Java, such as IDEs or servers. SEARCH %RUN_SERVICE% once the Elise notepad is opened 

Here, you have the following declaration towards the middle of your notepad file, search 

  • %RUN_SERVICE% -install ELC %JVM_DLL% %JAVA_OPTS% -Djava.class.path=”%CP%”  -Xmx768m -Xms64m -Delise.home=”%ELISE_HOME%” -start  
  • com.codegear.sanctuary.elise.Elise -params start -stop 

Modify the Xmx size to a bigger value (e.g. 1024m) and save the file.

Then Restart ELC Service, then go back into License Server status Page 

Additional Notes

The following lines contain other arguments for the ELC:  

  • -Xms64m (Initial heap size) 
  • -Xmx768m (Maximum heap size) 

If you want to chang the -Xmx value to your target size (e.g., -Xmx1024m or -Xmx2048m) you will need pen a command prompt window after modifying and saving the file, uninstall the service and then install it back. Then Restart ELC Service, then go back into License Server status Page 

Find the ELC System Status and confirm the current and max heap size now shows your new  value (e.g., -Xmx1024m). 

Make sure you speak to your system admin or IT prior to making any changes to your  Memory on the machine to ensure you are able to make these changes. 

If you need additonal assistance, please contact Support.
Copyright © 2026 Idera, Inc.