Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349057

Summary:	JS Web ide max heap larger than it needs to be
Product:	[Technology] EPP	Reporter:	David Williams <david_williams>
Component:	javascript-package	Assignee:	Project Inbox <epp.packager-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	minor
Priority:	P3	CC:	david_williams, thatnitind
Version:	1.3.2
Target Milestone:	1.4.0
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:
Bug Blocks:	347356

Description David Williams

2011-06-10 11:22:31 EDT

I'm not sure there is much harm, but noticed today that the JS IDE eclipse.ini has mx set to 512m ... probably copied over from Java EE IDE ... and there I wonder if 512m is enough! :/ ... but, Java has 384m, CPP has 384m (modeling has 512m). I suspect 384m is sufficient for JavaScript too. Actually, I wonder if we need an mx at all for JavaScript ... or, just "go with defaults"? 

Also, there might be some small risk in changing it, since some workspaces that were working simply might not work anymore if a user moved up to a newer version with less MX. Plus, only harm, that I know of, of being set "too high" would be users would "run out" of physical memory, not be able to run as many apps or instances, etc., if set way too high. 

So, unless end users complain, probably best not to change it. But, thought I'd open this issue just to document it, and see if anyone else knew of any implications.

Comment 1 Nitin Dahyabhai

2011-06-10 11:36:07 EDT

I'd say we need at *least* as much as Java given the way our models work, and very likely more.  512M seems like a decent value.

Comment 2 David Williams

2011-06-10 12:00:34 EDT

that's good enough for me! 

Thanks