I am looking to bundle JRE with my app, since that is Apple's requirement for submission to the appstore. Using the standard JRE libraries increases the file-size from 1 mb to 153 mb.
Can anybody recommend an alternative JRE that has much smaller file-size?
Found the solution:
Downloaded OpenJDK and deleted the files specified on this page. Reduced the size of JVM to 39 mb for me.
Related
What is the sweet spot PC configuration to download and build android AOSP (as of 2022)?
I am new to PC building and don't have much knowledge about PC
You can see the complete system requirements and recomendations at https://source.android.com/setup/build/requirements
A 64-bit environment is required for Android 2.3.x (Gingerbread) and higher versions, including the master branch. You can compile older versions on 32-bit systems.
At least 250GB of free disk space to check out the code and an extra 150 GB to build it. If you conduct multiple builds, you need additional space.
At least 16 GB of available RAM is required, but Google recommends 64 GB.
As of June 2021, Google is using 72-core machines with 64 GB of RAM internally, which take about 40 minutes for a full build (and just a few minutes for incremental builds, depending on exactly which files were modified). By contrast, a 6-core machine with a similar amount of RAM takes 3 hours.
All the info I can find basically says the 64 bit version is available but I can't find any info on what exactly that means? How is it different from the 32bit version?
From the release notes:
Large file support - Improved performance for large files, no size limit on 64-bit machines.
64-bit Windows builds - Use your computer's full address space with the 64-bit builds.
For example, to open large files (the 32 bit version has now a limit of 300 MB, previously it was 50 MB) you'll need the 64 bit version.
I have been trying to increase heap size max to 1440 of 4 GB ram, but still i am getting the Out of memory issue after two/three refreshes in two different browsers. I have set the VM aruments max to : '-Xmx1440m', while running gwt:run maven goal, but no luck. My system configuration looks as follows:
RAM : 4 GB, build tool: Maven, GWT, Java 1.6
Try to add -XX:MaxPermSize=256M.
It helps at least in Eclipse.
I have Eclipse Juno + latest GWT (GPE 3.1.2+ SDK 2.5.1).
It's just unusable :
Just hang-up now and then (ten times a day), so I have to kill and restart
At best very slow, meaning waiting minutes before UI response for trivial things
After WEB investigation, i did :
increased JVM resources in eclipse.ini
periodically purge the project folder "gwt-unitCache"
For some reason i also tried GWT on Indigo (as the GWT Designer does not run properly on Juno), but it is the same.
The issues seem to be yet somewhere else.
As there as performance issues posted on Google bug list, I am not too sure where I stand.
So my questions :
Does anyone use Eclipse/GWT with fair performances [on Windows ?
(is the issue related to windows -- which I doubt)]
Can anyone provide a set of configuration instructions which can
lead to a stable config ? -- or explain the traps to avoid ?
Before going to Vaadin I wanted to properly handle GWT, but i am close to drop it. Please help.
I would add RAM. 4 gigs sounds pretty slim for a dev machine. An OS with a few apps running will take up 2 gigs. Start eclipse and that's another gig or 2 easy. Then you start running jetty within eclipse for another gig or 2 and now you're hitting your virtual memory / page file which will slow it down tremendously.
Running firefox doing nothing else then looking at a single tab to test my app is 200MB of RAM. Some of my chrome tabs are 100MB easy. Just figure each browser tab eats 3-5% of your 4 gigs.
I'd say get at least 16GB on a 64bit OS and give eclipse and jetty at least 2 gigs each if not 4 each. A solid state disk (SSD) helps a lot too since compiling does a lot of random reads and writes.
Here's a screenshot of the debug settings with 3 gigs of RAM and some extra permgen space for subsequent refreshes of the pages. Just remember, if you run out of physical RAM and it starts hitting the page file these settings won't increase performance!
This might be a dumb/naive question, and if it is please excuse me :)
I have a brand new machine with the following specs:
Inter Core i7 2600#3.4GHz
RAM 8 GB
Windows 7
This machine has a 64 bits architecture.
On my previous machine, I used to install 32 bits versions of Eclipse and run it using a 32 bits JRE, and my current Eclipse setup works perfectly on the new machine.
I tried to install a 64bits version of Eclipse, and run it with a 64 bits JRE, and I am wondering if there are any compelling reasons to switch to this kind of setup or stick to my existing install. I guess that I would have to reinstall all the plugins, and maybe find that some of them are not compatible with the 64 bits version of Eclipse.
So far, the 64 bits version seems to need quite some more RAM than the 32 bits version, which is something that I expected, but nothing seems to have improved.
Thanks for your advice!
In general I use 64-bit Eclipse without problem, but there can be issues around plug-ins such as:
Adobe Flash Builder only works with 32-bit
The Subversion plug-in Subclipse needs a native 64-bit version of Subversion installed separately
There may be more but those are the ones I've encountered in the past.
Moving to 64-bit gives you access to more addressable memory but it won't speed anything up, in fact it might reduce performance in some cases (but nothing I see as significant to what I do).
Well the only thing that will improve is that you are able to use the advantages of 64bit. Other then that I'm not aware of any improvement.
For example what's better in 64bit is that if you have a very large project set you would be able to handle it more comfortably. For more information on 64-bit please look here
If you want to be on the edge of technology your choice would of course be the 64bit setup.
About the ram, this is expected because some of the Datatyps now use 64bit and are therefore larger to store in memory.
For most plugins you will get a 64bit version or alternative and so far for what I've used it it always worked.