Postponed (maintainer needs more info)
Project:
DrupalPro
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Jun 2012 at 06:08 UTC
Updated:
5 Aug 2012 at 09:31 UTC
Hi, when clicking on the links provided, to grab the ova, there is no 64bit option. When do you plan to post that .ova?
Thanks
Comments
Comment #1
mike stewart commentedFunctionally there aren't any differences - and VirtualBox is good enough now to run 64/32 on either a 63/32 OS.
However, my understanding is the footprint of 32bit is significantly smaller. It simply requires much less RAM (~half) plus smaller file sizes -- and small/fast is king as a VM. I've been meaning to run some benchmarks of both in a VM environment ... know of any?
What are the benefits of running 64? (If you can point me to some evidence that 64 provides real benefits, I'll take the time to burn a separate image)
Comment #2
AlanO commentedThere is a big difference in performance.
http://www.phoronix.com/scan.php?page=article&item=ubuntu_1204_3264&num=1
I'm currently importing this but I want to thank you for creating this. It's been a pain in the a** trying to use WAMP(my computer sounds like its dying) or Ubuntu(beside windows) trying to figure out what modules needs to be installed, how to fix the darn root permissions, etc. etc. I'm sure this will be of big help, thanks again.
Comment #3
elvis2 commentedMike, I agree small is good if you really want you quickstart / drupalpro to be portable. I am sure though there is an argument for performance, as AlanO stated. That is the camp I am in. I would much rather have better performance than smaller size.
Thanks for all the work you have done on this. I use quickstart just about everyday, it is a great blessing for us non-admin devs.
Comment #4
mike stewart commentedre: #2. thanks for the reply and the link. c-ray and postmark metrics seem most significant. However, still playing devil's advocate, I'm not sure that link is specific enough to demonstrate 64bit is truly better performance in a vbox setup -- especially when considering vbox only allows 50% of RAM and doesn't have direct access to disks. Even so, the gains in most metrics are nominal (less that 10-20% in most cases) ... and although I am sure that in a server setting, an optimized webserver with 64bit OS/apache is more efficient under a heavy load ... I'm just not convinced and haven't seen stats that can demonstrate similar gains for a single user system.
re: #3: small lends itself to performance.
Even so, I do plan to burn a beta3 image this coming week. I'll try to do a 64-bit. I'd love to see some metrics of both images -- to prove its either worth the effort/size for the 64bit. Even cooler if someone shared scripts they used to test ;-)
Comment #5
mike stewart commentedunassign from myself ... hoping someone might be kind enough to create/share some automated scripts for running metrics on a clean image.
Comment #6
elvis2 commented@mike I will ask my co-workers, since they are heavy in vm usage.
Comment #7
sonicthoughts commentedHi was about to go the drupalpro route, but concerned about performance / 64bit. Any updates?
Comment #8
mike stewart commentedMy experience is 32-bit is faster compared to 64-bit -- INSIDE a VBOX environment. (I run a 64-bit OS).
One of the main problems with 64-bit -- is it tends to require almost double the RAM (for everything) -- and running in a vbox environment you typically only have half the RAM available for any one instance.
So a typical scenario, on an 8GB machine, you'll have just less than 4GB to share with the guest OS. If you're on a 4GB machine (like me) -- the most I've been able to share is 1.92GB with vbox -- which isn't much for a 64bit OS running a LAMP stack and desktop -- but its TONs if you're running 32bit. I've been extremely happy with performance of 32-bit.
I'd also recommend waiting until tomorrw. I'll have the latest image then, which among other things, includes MariaDB by default, and is definitely faster than MySQL (at least my experience with it so far)
Comment #9
sonicthoughts commentedthanks for the fast reply! At some point I might want to put the system on bare metal, so I thought 64 would make sense ... but I'll definitely take your word for it.
I plan to start tonight - would be happy to try out the latest if you would like....
BTW - Other than 12.04 - what are the differences w/ Quickstart? Why the fork and not collaborate on Quickstart 2.0? Just curious.
Comment #10
mike stewart commented:) I would have preferred to collaborate. In fact, I started the quickstart 2.x branch ... and drupalpro is a fork of that code. I forked after current Quickstart maintainer felt Unity was too alien for future of Quickstart (I have to assume thats why Quickstart 1 built on 11.04 doesn't have unity). I like Unity more. I'm faster. It is keyboard based for power users -- yet also a simpler GUI for newbies. I ultimately want a desktop that is focussed on LAMP and developer/themer tools -- but in meantime, Unity is here and now. I needed something now, and simply wanted to share my work. I feel more choice is better.
As far as running baremetal -- it should work -- but you'll want to change your kernel (easy to do). But I use the kernel that is optimized for virtualization (aka, doesnt have a lot of drivers for hardware that it doesn't need) -- lends itself to a smaller footprint. One of the other things I'm doing with DrupalPro is making the setup script friendlier -- so you can simply install Ubuntu, add GIT, clone DrupalPro code, then run the setup scripts. (Still in beta! and unless you backup to beta2 image, current code is not well tested)
1204 and the standard Unity desktop are by far the biggest changes. I've also ripped out fewer things. I felt things like accessibility and CUPs printing are too important. I'm also not fully setting up SAMBA... but optiing to just make it easy. I've also installed a firewall by default. and Multiple partitions, to make it easier to grow. Otherwise, I've tried to make DrupalPro more like vanilla Ubuntu -- with some sprinklings of Drupal goodness -- such as customized bash_aliases for GIT, or a useful cheatsheet for the desktop, etc. One of my goals is to make it easier for people to find things, (such as all the log files needed for LAMP) and the apps they'll find useful for dev/theming -- or at least easy for them to install -- but I'm really avoiding messing with Ubuntu configurations as much as possible.
Hope that helps a little ;-)
Oh, and support :) -- I use IRC -- so if you need help,, come visit in #drupalpro
Comment #11
sonicthoughts commentedThis is a fantastic project - thanks! I've hit a major performance snag though. vanilla ubuntu unity 64bit seems to fly but I'm finding this version quite slow - At this point id be better off using a 3rd party host. quad core fast CPU, 8GB Ram. doubt its the hardware. not sure if it's the 32bit but spent a few hours with little success.
Comment #12
mike stewart commentedSounds similar to my specs. only more RAM. So I'm surprised. What is HOST OS? Also, what version of Virtualbox -- you may need to re-install guest additions. The beta2 image was built on Virtualbox 4.1.16 .. and if you're using 4.1.18, you may need to reinstall.
Comment #13
heyyo commentedI have the same config than sonicthought intel i7 3770 + 8GB on asus motherboard with chipset Intel H77.
I also have a really severe slow issue, but only if i'm in fullscreen mode with 3D acceleration enabled.
I'm not sure to understand why 4.1.16 is recommended over 4.1.18 ?
Comment #14
heyyo commentedI resolved all my issues related to fullscreen mode with 3d acceleration enabled with unity 3d.
first you need to install compizconfig-settings-manager using sudo apt-get install compizconfig-settings-manager.
Then in Preferences->Compizconfig-settings-manager look for Utility. And then 'check' the workaround item. Finally in the settings for the workaround item, look for 'Force fullscreen redraws (buffer swap) on repaint' and check this option. Thats it!
Solution found in this virtualbox ticket:
https://www.virtualbox.org/ticket/8858