why is sugarcrm very slow in VM?

[bnnzx]

I installed the sugarcrm ce 5.52 on vm which os is linux and network adapter is Host-only. When I visit sugarcrm in a intranet network (the linux can access internet), it is normal. However, when I do not connect the computer to the intranet and use it independently, the performance of sugarcrm is too slow to stand.
I am not sure that sugarcrm ce will visit sugarcrm official website in background or not. Maybe it is the point.
Can you give me a hand? Any hint is welcome.

[roblaus]

This exactly is the reason. Login as admin and go to admin/Sugar updates and uncheck the boxes there. Save. This will prevent Sugar from calling home and should solve all your speed problems.

[kuske]

Open the config.php and search for "sugarbeet".

Thsi should be

'sugarbeet' => 0,

[mccon1]

I've noticed that perf problems can be caused by some browsers, especially Firefox.

With Firefox 10 (all addons disabled), the pages load incredibly slow (5 sec or more).
With Chrome 15, pages load significantly faster (around 2-3 sec. each)...

--Frosty

[morrighu]

Make sure you have enough system RAM.
According to the documentation, you need 2GB. Even for a VPS where you can "burst" above your pre-paid limit, it pays to have it when the system needs.

Disable any apache modules you aren't using.
Disabling modules you don't need reduces Apache's memory needs, often siginificantly.

Try modifying your apache2.conf to optomize performance.
The two things below should give you a place to start. You'll need to watch the server and tweak as needed based on your traffic. YMMV.

<IfModule prefork.c>
StartServers       3
MinSpareServers    2
MaxSpareServers   3
MaxClients      15
MaxRequestsPerChild 5000
</IfModule>

And

KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 2

Try modifying your /etc/php5/php.ini to optomize performance
If you are already at or above 64M, try increasing it.

php_value memory_limit 64M

Try modifying your /etc/mysql/my.cnf to optomize performance
Again, if you are at or above these memory limits, try increasing them to see if they have an impact on your problem.

set-variable=max_connections=15
set-variable=max_user_connections=15
set-variable=query_cache_limit=16M
set-variable=query_cache_size=64M
set-variable=query_cache_type=1