News for hackers. Stuff that matters.
Re:Firefox fixes save gigabytes of memory on image-heavy pages by patrickaljord on Tuesday October 01, 2013 @09:29AM (#6475935)
isn't 16GB enough to run an extra VM for dev? also, try docker.
Re:Firefox fixes save gigabytes of memory on image-heavy pages by aktau on Tuesday October 01, 2013 @12:02PM (#6477006)
Not when most of that 16GB is in use. At the moment, chrome is using up 3.4GB. Yea, I have a lot of tabs open. Yes, I should work on that. Yes, I'd also like being able to open that many tabs and have my browser perhaps release some of that memory and just reclaim it when I open the tab for reading again.

Docker is real nice, although I might go for pure LXC the nex time I build something. But I'm developing on OSX (as many of us, I believe). So _not_ running a VM is not really possible here. I deploy on Linux, and like to have my environment very consistent, hence the VM. Granted, with Docker/LXC I could probably get by with just one VM and a lot of little apps running side-by-side, but that's not how my current setup and projects work, yet.

At any rate, less memory used by browser is more memory for me, to use any way I want.

I already love the firefox behaviour that when it restores your tabs, it doesn't actually load them until you click on them. Awesome startup speed improvement.

Re:Firefox fixes save gigabytes of memory on image-heavy pages by gamache on Tuesday October 01, 2013 @04:55PM (#6479039)
I'd also like being able to open that many tabs and have my browser perhaps release some of that memory and just reclaim it when I open the tab for reading again.

Chromebooks do a great job of this -- inactive tabs are often freed when memory is needed elsewhere, and reloaded as necessary. I wonder if that feature is going to come to Chrome outside of ChromeOS.

Re:Firefox fixes save gigabytes of memory on image-heavy pages by jordanthoms on Tuesday October 01, 2013 @05:25PM (#6479179)
That's also done on Chrome for Android.
Re:Firefox fixes save gigabytes of memory on image-heavy pages by staktrace on Tuesday October 01, 2013 @07:13PM (#6479684)
And Firefox for Android.
Re:Firefox fixes save gigabytes of memory on image-heavy pages by darkarmani on Tuesday October 01, 2013 @12:47PM (#6477320)
Did docker add Windows and Darwin support already? Wow, they are really moving fast.
Re:Firefox fixes save gigabytes of memory on image-heavy pages by darkarmani on Tuesday October 01, 2013 @05:17PM (#6479145)
The joke being that Docker requires LXC and aufs, which means you are stuck running Ubuntu for now. Fedora is soon going to announce Docker support when 0.7 is released.

For now if you want to run docker on your Mac, the best bet is to use Vagrant + virtualbox (or fusion if you have the provider). This means you have to run another VM to run docker which defeats the purpose of the suggestion of running Docker, so you don't have to run another VM instance.

Re:Firefox fixes save gigabytes of memory on image-heavy pages by outworlder on Tuesday October 01, 2013 @06:09PM (#6479378)
Yes.

But then, you can run a single VM with any number of Docker containers inside. Depending on what you are doing, that could be a win.

Re:Firefox fixes save gigabytes of memory on image-heavy pages by ritonlajoie on Tuesday October 01, 2013 @06:36PM (#6479521)
if you are running one docker per VM, you are probably doing something wrong :)