Hi I am pretty new to Drupal and am still trying to finish my first Drupal site...
I have apparently installed too many modules. Even though I have switched to a VPS, the site is still a little slow. I have uninstalled as many modules as I can and am thinking of creating two drupal sites, dividing the modules to those two sites while at the same time have the users and information shared before those two Drupal installation.
I found http://neemtree.com.au/sharing-content-users-and-configurations-across-m... and http://drupal.org/node/201673 and am confused how these two methods are different from each other.
What I want is:
1. Keep all the modules I have right now and be able to install more if I need to in the future.
2. The users should never know that they are visiting different Drupal sites (never have to sign up twice, sign in twice etc)
3. All content on those two (or more) Drupal installation are being shared and updated at the same time and can be used on either site.
4. If those two methods (see links above) both do the same thing, then I hope to choose one that is easier to maintain when upgrading Drupal etc.
Your ideas will be appreciated!! Thank you =)
Comments
=-=
have you double checked your memory settings using phpinfo() ?
while your account may have 256M dedicated to it, I don't know that it means your account will default to using it.
administer -> status report will tell you how much ram PHP is set to use as well.
PHP memory limit: 64M
Hello again VeryMisunderstood,
is this why my site is so slow? Status Report: PHP memory limit 64M
Should I change it to 2560M in WHM or do we usually do it on cPanel?
Many thanks!!
how much u are paying for
how much u are paying for the VPS?
get a more powerful CPU, get more RAM. Do some performance turnings, in Drpual, MySQL, PHP etc.
Forget the multiple sites idea.
Paying for 256M of RAM
Do you know how I can find out if I am using what I am paying for already - that 256M?
WHM where you control the entire VPS or cPanel?
I did what I can on the performance tuning part
What are the reasons to completely ignoring the multiple sites idea?
Thanks
=-=
I'd use php.ini and bump the memory up though I don't know that I bump it all the way up to 256. I'd start with 128.
mutisite in your situation won't help in the way you think it will. your ram and your sites will still be on one account thus using the same resources.
In a similar thread you were asked to run the devel.module and to look at the amount of queries being run. Have you done this?
Last but not least to get to the bottom of this. I'd start disabling modules one at a time. All of them until I find which module may be causing the slow down. It is not impossile that there is a problem with a module that you are using.
another way to test this would be to create a subdomain, install a vanilla drupal and are the same problems recognized?
Devel
Hi VeryMisunderstood and everyone,
I hope everyone had a good weekend. Thanks again for your help.
I have just installed Devel and actvated it but I get this error message:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 505250 bytes) in /home/myhost/public_html/drupal_site/sites/all/modules/devel/devel.module on line 1428
I already changed this line from 60M to 128M in my php.ini file, but not sure if this mean that this is what you suggested:
memory_limit = 128M ; Maximum amount of memory a script may consume (128MB)
and this is the result i got from Error Reporting:
Executed 199 queries in 72.37 milliseconds. Queries taking longer than 5 ms and queries executed more than once, are highlighted. Page execution time was 7329.67 ms. Are these numbers normal?
What would be the downside of
What would be the downside of bumping the memory limit up?
=-=
if you exceed your hosts RUP, then you can be kicked off the servers with no refund.
site is still a little slow
to make it faster turn on the drupal caching here http://[www.yoursite]/admin/settings/performance.
Please dont try new things on deployment server always have a backup.