previous      content      next
Scalability

To avoid infinite growth of collected data, it is possible to limit the number of events to be recorded in the profiler agent and processed in the profiler UI.

  • When writing a probe: table API method Table.setMinimumRecordedLastingEventTime() allows to avoid recording of non-interesting short events. See the method's Javadoc for detail. Built-in probe AWTEvents is an example of using the method.

  • In profiler agent: startup option probetablelengthlimit=<number of rows> limits the number of rows to be stored by the profiler agent per table. If a table reaches the limit, it will no longer be populated. Default value is 20000.

  • In profiler UI: property -Dyjp.probe.table.length.limit=<number of rows> limits the number of rows which the profiler UI reads for each table when a snapshot is loaded or a running application is being profiled. Specify the property in <Profiler Installation Directory>/bin/yjp.ini

    By default, 20000 rows are loaded.

previous      content      next