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.
Related
I am running a Fedora 24 OS (with GNOME 3) and I just installed the eclipse CDT package from the Fedora repositories (Eclipse CDT Neon.1), and it turned out to be extremely slow, but only when writing code or scrolling, the rest of the UI works perfectly and really quickly.
I have done some research about the topic and seemingly this problem is usually related to the GTK backend, and is commonly solved by running eclipse under GTK2 instead of GTK3. However, this has not helped me at all. The options I have tried are:
export SWT_GTK3=0
And
eclipse --launcher.GTK_version 2 (also tried in eclipse.ini)
These two options effectively switch to GTK2, which is noticeable because the graphical appearance changes.
I tried also older versions of Eclipse (Juno, Kepler and Luna) and the problem still exists, probably even worse. I have increased the memory size for the JVM to 3GB and the problem remains intact.
The underlying hardware is a 6 core Intel Xeon (12 virtual cores with Hyperthreading) and 32 GB of RAM, so I assume this should not represent a problem.
I also noticed that while scrolling or writing, one of my cores goes to 70%-100% utilization, which explains the lag, but I don't know how to solve.
Is there any other option I can try?
I need to test my C code for 32- and 64-bit versions of Windows (XP and 7) and Linux. But I have got access only to their 64-bit installations.
Question: Is it possible to use some boot-time settings or other hacks to run/emulate these OSes in 32-bit mode? If not, is there any other way to test the portability of my C code?
Note: The C code in question is not a full-fledged application but rather a .dll/.so file.
Neither Linux nor Windows 64Bit can run as 32Bit OS. Also, while you can run 32Bit executables on the 64Bit OS, it is not quite the same as running the same under a 32Bit OS. But it might work as a quick screening test. Besides, you certainly want that to work as well, right?
Your choices are full multi-boot setup, using VMs (might hide/expose bugs), being content with the emulation layer or running the other OS's on different hardware.
BTW: If you have Windows 64Bit, the license allows you to run 32Bit instead and vice versa. Anyway, you might want to check different language versions as well...
Does RethinkDB not offer 32 bit versions?
RethinkDB's download page has download links to various *nix packages, but all of them pertain to 64 bit architectures.
Is there a 32 bit version or is it simply not supported?
Edit: We've just added 32-bit support in RethinkDB 1.3, see how to install it at rethinkdb.com/docs/install.
Original answer:
RethinkDB is currently only available for 64-bit architectures. We may offer 32-bit support in future versions of RethinkDB.
I'll be sure to pass a note along to make the download page clearer about prerequisites.
This may be a silly question but should I use the 32 bit or 64 bit version of Eclipse on my Mac?
I'm fully up to date with Snow Leopard and all patches and I have a pretty recent iMac (30", Dual Core, 3GB)
I thought that Java on Snow Leopard was now 64 bit only so can't understand why there is a 32bit download. Is it just the Eclipse download page that is showing 32 bit for older versions of OSX?
You're probably better off with the 64-bit edition. Nearly all the system software is 64-bit in Snow Leopard, and if you only run 64-bit apps, you don't pay the cost of having to load the 32-bit runtimes (which can consume quite a lot of memory). It may also benefit from the 64-bit memory model, though I'm not sure how well the JVM takes advantage of that yet. I expect the 32-bit version is provided for Leopard (and earlier) compatability.
I would use 64bit Eclipse.
safe bit is 32-bit :)
I've just changed computers at work and now have a really beefy 64bit Vista os. Currently I'm still slogging through the pile of quirks (like no 64bit drivers for ms access) and I've noticed that my startup time for eclipse is a LOT longer than it was on 32bit Vista. I have almost nothing in my workspace yet, so that knocks out most of the change/rebuild workspace issues. I've used the -clean option a few times and nothing seems to change it.
I'm not running the 64bit version of eclipse, just because it seemed like too much trouble right now with all my other issues getting the machine back into a stable state. It also seems like 64bit eclipse is still pretty rough around the edges since it doesn't appear to have actually been released yet.
Any clues about what I can try to speed things up? Once it's running, it seems to work fine.
TIA
Try tweaking the JVM's memory settings. E.g., if you have 512 MB memory, pass "-vmargs -Xms40m -Xmx256m" to eclipse.exe.
You may give eclipse 64bits a shot (even though you say in your question not using it).
With the latest JDK (6u12) and the latest 3.5M5 eclipse, it does work quite fine.
With my settings, that is ;)