Bug 413515 - Enhance log provider performance
Summary: Enhance log provider performance
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Server (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: 4.0 M1   Edit
Assignee: Maciej Bendkowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-23 08:33 EDT by Maciej Bendkowski CLA
Modified: 2013-09-06 08:39 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Bendkowski CLA 2013-07-23 08:33:38 EDT 
Log provider should not expose logs using JSON. In order to build a JSON response, the whole log file, which might be arbitrary large, has to be cached in the server memory. JSON responses should provide only log file (appender) metadata, within a direct download link would be present. Also, investigate the log buffer optimum capacity.
Comment 1 Maciej Bendkowski CLA 2013-07-24 08:00:19 EDT 
Pushed to master with:
http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=4beced1b21acf4cf5b5b61a8b4ad65f47d60c7e8

http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=f7520a21faf95090460e971a5e274af381361df9

Logs are now resource-based. Like in git, they have the shape and linked resources concepts implemented. Log file contents are now accessible only in raw format, where JSON format support the metadata retrieval. The buffer used in passing log files to the clients is set to 64 KB by default. Nevertheless, it might be customized using the Orion configuration file as this parameter is strongly instance- and use-case-dependent. Appropriate changes will be documented on the wiki page.