No Official ICS for LG Optimus V :(

[JerryScript]

It's amazing how one little change in hardware can make a huge difference. When I built the computer I use to compile BACKside, I bought a 24" monitor. My nephews at the time were playing their computer games on an old 17" monitor, and as an old school gamer, I couldn't bear to watch them this way, so I gave them my 24" about a year ago. Well, for xmas, they returned the favor, and they got me a new 24" HD TV/monitor.

So I had been compiling while using the 17" and could normally get a complete build using -j4 in about 45 minutes. Since hooking up the 24" HD monitor, I haven't been able to compile at all till this morning, and I had to resort to a basic make with no -j*, so it took at least twice as long. Seems so much memory is being used to support the HD desktop, it runs out of memory when dexing the frameworks or server. I've spent the past week in frustration thinking I had messed up my local repository, or borked my build environment. Guess I'm going to have to shell out for more memory, or be more patient.

 

[kcls]

Well that stinks. I hate those presents that are awesome, but then require shelling out more money to make them work the way you want Being a noob at building ROMs (I started compiling cm9 for my nook on Wednesday, its my first ever Linux experience, lol) I probably would have gotten mad and cleared out my vbox machine and started over

Tapatalkin it from my IHO CM7.1'd, MIUI Themed Optimus V

 

[tdm]

It's amazing how one little change in hardware can make a huge difference. When I built the computer I use to compile BACKside, I bought a 24" monitor. My nephews at the time were playing their computer games on an old 17" monitor, and as an old school gamer, I couldn't bear to watch them this way, so I gave them my 24" about a year ago. Well, for xmas, they returned the favor, and they got me a new 24" HD TV/monitor.

So I had been compiling while using the 17" and could normally get a complete build using -j4 in about 45 minutes. Since hooking up the 24" HD monitor, I haven't been able to compile at all till this morning, and I had to resort to a basic make with no -j*, so it took at least twice as long. Seems so much memory is being used to support the HD desktop, it runs out of memory when dexing the frameworks or server. I've spent the past week in frustration thinking I had messed up my local repository, or borked my build environment. Guess I'm going to have to shell out for more memory, or be more patient.

I know what you mean. I have a 2gb AthlonX2 and its painfully slow. I do similar builds at work (compiling embedded products) on 16gb 12 core boxes.

Anyone try ccache against Android builds? Not sure if it would make much of a difference as most of the work is probably java, linkage, and packaging (including optimizations). Is there a java equivalent to ccache?

 

[LeslieAnn]

Okay, after hearing some of this...

I'm trying to figure out an easy way to set it up so you guys could build off my old desktop (Intel Q9550/8ggigs ram/40GB ssd/1TB WD Black). If I can round up a power supply (easy enough) it would speed you guys up a lot, or at least allow you to offload the work. I know I could setup VNC and/or SSH and port forward the router easily enough, the question would be where to go from there.

If you guys have any ideas on how to share this thing, I would be happy to hear them and see what we can do, as it stands the system is just sitting on a shelf doing nothing.

 

[tdm]

Okay, after hearing some of this...

I'm trying to figure out an easy way to set it up so you guys could build off my old desktop (Intel Q9550/8ggigs ram/40GB ssd/1TB WD Black). If I can round up a power supply (easy enough) it would speed you guys up a lot, or at least allow you to offload the work. I know I could setup VNC and/or SSH and port forward the router easily enough, the question would be where to go from there.

If you guys have any ideas on how to share this thing, I would be happy to hear them and see what we can do, as it stands the system is just sitting on a shelf doing nothing.

 

[tdm]

Okay, after hearing some of this...

I'm trying to figure out an easy way to set it up so you guys could build off my old desktop (Intel Q9550/8ggigs ram/40GB ssd/1TB WD Black). If I can round up a power supply (easy enough) it would speed you guys up a lot, or at least allow you to offload the work. I know I could setup VNC and/or SSH and port forward the router easily enough, the question would be where to go from there.

If you guys have any ideas on how to share this thing, I would be happy to hear them and see what we can do, as it stands the system is just sitting on a shelf doing nothing.

Thats a very generous offer thanks. I will probably get more RAM soon.

I have a Xen VPS that is short on disk but is scheduled to get an upgrade "soon". When that happens it should also help. If anyone wants to share for a couple bucks a month let me know and I will get you a login. Its with prgmr.com I highly recommend them.

 

[tdm]

Okay, after hearing some of this...

I'm trying to figure out an easy way to set it up so you guys could build off my old desktop (Intel Q9550/8ggigs ram/40GB ssd/1TB WD Black). If I can round up a power supply (easy enough) it would speed you guys up a lot, or at least allow you to offload the work. I know I could setup VNC and/or SSH and port forward the router easily enough, the question would be where to go from there.

If you guys have any ideas on how to share this thing, I would be happy to hear them and see what we can do, as it stands the system is just sitting on a shelf doing nothing.

Sorry for the blank replies im typing on my phone.

One option for sharing is a VPN. I would be happy to set you up with an openvpn key on my server if you like. Then you can ssh to my box and hop over to your desktop.

 

[LeslieAnn]

The networking side is easy, it's just how best to setup the box most efficiently for multiple users.

 

[tdm]

The networking side is easy, it's just how best to setup the box most efficiently for multiple users.

Not sure exactly how much I would have to input about that. Windows or Linux?

 

[LeslieAnn]

It would have to be Linux for the build and there is little point sing Windows and then VM Linux on except with option 2..

The simplest option is multiple users, but I'm not sure how ssh console works with multiple user logins at the same time. I may have to test it.

Another option is virtual machines, one for each user. Unfortunately performance would suffer considerably as more and more ran, regardless of being used or not. For me, this is the most familiar solution, but it's not very practical here.

The last option is setting it up so each persons home system acts as thin client to the server. This is probably the best method, but the one I am least familiar with.

 

[tdm]

It would have to be Linux for the build and there is little point sing Windows and then VM Linux on except with option 2..

The simplest option is multiple users, but I'm not sure how ssh console works with multiple user logins at the same time. I may have to test it.

Another option is virtual machines, one for each user. Unfortunately performance would suffer considerably as more and more ran, regardless of being used or not. For me, this is the most familiar solution, but it's not very practical here.

The last option is setting it up so each persons home system acts as thin client to the server. This is probably the best method, but the one I am least familiar with.

There is no need for any complicated setup, VMs or anything. It will Just Work. ssh does not need or give access to a physical console (like you would use when you setup Linux in VMWare on your Windows desktop).

Some suggestions, if I may:

* You probably have a distro of choice. If not, my avatar should hint at mine.

* Put the root filesystem on the SSD and /home on the WD. I can assist with detailed partitioning if you like.

* Don't tear up your SSD with swap, put the swap space on the WD. Linux likes a little swap but too much is wasteful. I'd recommend 256mb to 512mb. Unless you plan on using hibernate (suspend to disk), in which case you'll want a bit more space than your RAM, but I don't expect that you will.

* When setting up sshd, never allow root via ssh. I highly recommend not giving root a password at all and relying on sudo instead (like Ubuntu does by default).

* Install the SDK and NDK in a shared location (/usr/local/android-sdk, /usr/local/android-ndk). This will be on the SSD per above. This will involve some massaging of file permissions, as the SDK and NDK are not normally installed in shared places. But it works, and works well -- I have done it on a couple systems. I compulsively install things in /usr/local and never in my /home. I can shoot you a tarball if you like, or give you detailed instructions on how to change the permissions.

Hope that helps.

 

[LeslieAnn]

That is exactly the type of info I needed.
I wasn't sure how SSH handles multiple users as I have only ever used it in a single user setup.

Sharing the files would probably be a bit of a hassle for me, I can handle Linux but I can get over my head at times. Eventually i get it, but searching up help online can be a nightmare.

As for the drives, I will probably keep it simple and just pass on the SSD. Once spun up the speed difference isn't so bad between them. Plus, if it's the OS alone on there, the benefits diminish fast, the SSD hits a transfer rate bottleneck limiting it to half speed, which is one of the reasons I upgraded the system.


You confirmed pretty much exactly what I was hoping for and figured would work.
Hopefully I can get a psu tonight.

 

[tdm]

Well to answer my original question two of the first links that come up on google for "ccache for java" say that (1) java compiles so much faster than c++ that ccache would not be that useful, and (2) using ccache to compile Android (the c/c++ parts) can reduce full build time by 40% or more.

 

[JerryScript]

I use ccache, it does improve build times, but I would say by about 15-20%

 

[tdm]

That is exactly the type of info I needed.
I wasn't sure how SSH handles multiple users as I have only ever used it in a single user setup.

Sharing the files would probably be a bit of a hassle for me, I can handle Linux but I can get over my head at times. Eventually i get it, but searching up help online can be a nightmare.

As for the drives, I will probably keep it simple and just pass on the SSD. Once spun up the speed difference isn't so bad between them. Plus, if it's the OS alone on there, the benefits diminish fast, the SSD hits a transfer rate bottleneck limiting it to half speed, which is one of the reasons I upgraded the system.


You confirmed pretty much exactly what I was hoping for and figured would work.
Hopefully I can get a psu tonight.

I'd still recommend putting /home on a separate partition, mainly because it makes system upgrades and backups easier. Trust me, it's trivial on the front end and can save a big headache down the road.

I'd also still recommend setting up the SDK and NDK in a systemwide shared place. It's not a huge deal but there is obvious disk savings and some potential for runtime savings as well, if more than one person is building simultaneously. And you _are_ building this box with multiple users explicitly in mind. It's not that hard, really.

 

[LeslieAnn]

I'd still recommend putting /home on a separate partition, mainly because it makes system upgrades and backups easier. Trust me, it's trivial on the front end and can save a big headache down the road.

I'd also still recommend setting up the SDK and NDK in a systemwide shared place. It's not a huge deal but there is obvious disk savings and some potential for runtime savings as well, if more than one person is building simultaneously. And you _are_ building this box with multiple users explicitly in mind. It's not that hard, really.

I was thinking along similar lines, sounds like a good plan.

 

[LeslieAnn]

Unfortunately, I was stuck working late all week and never got a power supply.
I ordered one from Newegg on Friday and it will be here Monday, with luck I can get it up and running that night.

 

[tdm]

No worries here I appreciate just that you're willing to share a build box.

I priced out some parts and will probably get an quad CPU and 8gb ram shortly.

 

[LeslieAnn]

Look for sales, another 8gigs of DDR3 is only about $30. More is better than faster (I.M.O.)

My old quad system was nice, and I know many drooled over it, but the new one absolutely crushes it.

 

[drezliok]

I'm sitting on a 2003 Thinkpad T30, 2.2ghz with 1gb of ram. For a desktop I have an old P4 3.2 ghz with 4gb of ram [running at 3gb]

I have a Tri-core AMD based system waiting for a power supply in the corner collecting dust.
(I'm a father of 2, with a wife in college, and living off what I make as a gas station crewleader. Sucks but I get 40+ hours in a really bad area economically)

Jealous to say the least.
Thankyou for using that hardware to build wonderful roms!