So I am running a VirtualBox VM for a Big Data Programming class I am currently in. I'm not entirely sure what kind of specifications to mention to provide any insight, but I have around 95GB of memory left on my Macbook Pro. I have to code in Eclipse Luna in the VM, but once the VM is up and running, opening up Eclipse takes an obscene amount of time. Is this a memory issue, and would buying an external hard drive be the best course of action? When I brought this issue to my professor that seemed to be his consensus(its a memory issue), but I wanted to get a wider array of opinions/help.
So it sounds like you have a RAM bottleneck. Try increase the amount of RAM allocated to the virtual machine. In VirtualBox:
Power off your virtual machine in Virtual Box
Select the virtual machine you are using
Click on Settings
Click on System
Increase the amount of RAM "Base Memory" dedicated to the virtual machine
Click Ok.
Note: Be sure to not add so much that you make the host go slower. Try testing with different amounts until it is optimal performance.
Here is a possibly related resource to help you resolve your problem:
https://forums.virtualbox.org/viewtopic.php?f=8&t=39368
Related
is it possible to replace a ram with higher storage on a machine with a processor of low speed? is speed of processing increased or decreased.
i want to replace the ram drive of my machine with a higher storage ram so that I can try to manipulate the processor speed without changing the processors, will it work?
Yes. You can use faster RAM, currently up to DDR4-4800MHz. Using higher capacity RAM would also be useful if running out of RAM capacity is what’s slowing you down. Using a high-speed solid-state drive (SSD) would also speed up task that require reading or writing from storage, including booting up the computer and running programs that use a lot of assets on the computer. You can also overclock both your CPU and RAM to make them faster, but this may void your warranty.
Additionally, you can use software. For example, you can use CCleaner to remove useless files which clutter your computer. You can also use it to disable unneeded scheduled tasks that your computer runs. If your computer has a spinning-disc hard drive, then you can try defragmenting it by using the built-in Windows defragger, or you can use the Defraggler program from the same people who make CCleaner. Of course, you can also try deleting programs or files you no longer need or use if it’s limited hard drive capacity that’s slowing you down.
If it’s web browsing that’s slow, you may want to consider using a faster browser, like Google Chrome or Firefox. You can also install browser extensions/add-ons like AdBlock and Ghostery to prevent unneeded things from being loaded on pages, making pages load faster.
I am trying to run predictive modeling on large volume of data and this requires large amount of RAM (>8gb which i currently have on my laptop).
Just wanted to check if any of you encountered similar problem ? I recently came across external RAM for windows 7 OS - wondering if any of you have tried it ?
Does it help if i get an "readyboost RAM" of say 25gb or higher to solve this problem ?
Please let me know if its worth investing in external readyboost RAMs ? Thanks.
I use a 16Gb Memory stick on a 4Gb laptop - Windows 7 will only use 4Gb.. not sure if physical memory and the amount of Readyboost memory that Windows will use are related. I must say it does make a difference. Worth a look with USB memory sticks being so cheap now.
It certainly seems to speed up program startup and makes the system feel more responsive. A good cheap investment.
How much ram and processing power are required to run eclipse smoothly?
I plan to build plugins by extending EMF, GEF.
If you want to be confortable to build plugins, 2GB of RAM is a minimum since you would need multiple Eclipse instances (at least the instance where you have the code of the plugin and the instance where your plugin is running). For the processor, pretty much anything released in the last 4 years (except low end processor) and you're good.
I had a Core 2 Duo with 2GB of RAM a year ago and while it was a bit slow from time to time, I could do my job with 2/3 Eclipse instances. Now with a Core i7 and 6GB, I run daily with 6+ Eclipse instances without feeling any problem.
Stephane Begaudeau
The minimum requirement (2gb) mentioned for eclipse is meant for capability of using it. More Ram is good but less is punishing.
For Eclipse Plugin development, I suggest 8gb of Ram. The CPU choice depends on budget. I had i5 3rd gen and I'm sure it would handle plugin development easily. I won't suggest anything lower than i5 3rd gen or i3 5th gen or ryzen 3 2nd gen or ryzen 5 1st gen.
With my experience I'm telling. When I open 1 extra eclipse instance, few browsers tabs, few more applications like postman, the ram usage spikes to 90+ despite of having 8gb ram. Also, I've octa core machine and sometimes I'm able to utilise it fully 100%. Hence, more is good, decide according to budget.
You must not cut cost in RAM. 8gb is the sweet spot for your need. 4gb will perform slow for sure unless your usage is very low like using only eclipse.
Eclipse java code responsible for long time operations(index update) is mostly singlethreaded, so it is 2-core(there is no one core proc on the market with normal power), i think i3 and overclocked as high as possible. 4gb of cheap ram is quite enough, you don't need fast ram for that. I've also suggested small size SSD raid for HDD is you have enough money. But actully it is not about hardware. It is about eclipse algorithms, memory management, bugs and usability.
I thought of migrating from J 1.5.23 to 1.7 and like almost everyone i too ran into problems (Good i backed-up my site)
The problem i am facing is that my jUpgrade gets stuck at 'Migrating undefined'. 1.7 gets downloaded completely and also extracts correctly. I think i am still facing this problem because i somehow run out of space during the installation. what i wanted to know was How much disk space does migration require?
I have like 25 Mb free on my server and i am allowed only 100 MB so.
Thank You?
and btw i also unchecked the skip downloads options, didnt work for me
You will probably need more disk space than you have available. Your current site, plus the downloaded zip file, plus space for extracting the files plus any backups you have on the server are likely to exceed your 100MB.
I'd recommend taking a backup of your site, setting up the site on a localhost (xampp, wamp, etc) server on your own machine and run the migration there. This will have the benefits of not hitting arbitrary limits of what sounds like a very low budget web host.
Obviously you'll have the extra complexity of setting up your own server on your PC - but there are many tutorials out there that will walk you through the process, and the learning of new skills is always good.
I have written an application in Java using Eclipse IDE and I now need to know the minimum JRE version that is required to run the application! I know that certain methods are only available under later JREs, but I was wondering what the easiest way to find out the highest requirement of my application would be, so any suggestions would be appreciated...
Also whilst I am on the topic of requirements, I would appreciate any advice or methods for determining the minimum system requirements for my software in general - i.e minimum amount of RAM...
Thanks in advance
Method 1: For minimum JRE version, that's going to be tough. The easiest way is to simply require the same version that you're building against, or later, e.g. JRE 6.x.x or higher.
Method 2: Install multiple JDK's, making them available in Eclipse, and just change the version you're building against, running your app's test suite each time, and making sure they all pass. The earliest version of the JDK that allows all your tests to pass is the lowest JRE it can run against. Simply having your app successfully compile isn't enough, because previous versions of the JRE/JDK might have bugs that allow for successful compilation, but don't allow for proper program execution.
Method 3: Always require the latest on the client side, because Oracle is constantly patching security holes, and ultimately, it may be best to require the latest versions, if you have that kind of control, on the client side.
As far as RAM, that's easy. When the JVM starts it sets a 'maximum' amount of RAM (I believe the default may be 128MB), and that's a hard limit that your application cannot exceed without crashing. Profile your app over time, tweaking the memory settings on the JVM, and find out what the minimum amount of RAM is that you'll need for your app to run both (a) with acceptable performance, and (b) without throwing an OutOfMemoryError, and you're done.
Ref: How to configure JVM options and memory?
For other requirements such as CPU req., things get a little fuzzier. There are a lot of CPUs out there, and the throughput that a given system produces can vary not just based on CPU speed, but the speed of the hard drive, the amount of RAM installed in the system, the speed of the network interface (if you're writing a network app), and other things. For requirements such as that, you'll want to just test it on a variety of systems and sort of draw a line somewhere, and say, "You can expect acceptable performance if you have hardware that is at least as powerful as X, Y, Z".
The other thing you could do is build in a benchmark, or some kind of performance logging, and have that performance data sent back to you. Lots of apps do this. You know that "May we send anonymous usage data back to the mothership?" question you get when installing some software? Well, common among that data are system-specific details such as RAM, CPU, hard drive model, and other hardware details (whatever data you determine is relevant to your app), along with performance logging data. By taking that kind of approach, what you get is a lot of performance data from lots of different system configurations without needing to have a huge number of differently configured machines in-house.
You can do the same thing for program crashes and bugs - have the stack traces, system info, and other relevant data dumped to a log file that is sent back to you - but of course, only if your users have said it's okay to send that data back to you.