<div dir="ltr"><div><div>Hi<br><br></div>If you are going with H/w solution best way is to separate MySQL server from Webserver and use SSD or ideally <a href="http://www.makeuseof.com/tag/ram-drives-faster-ssds-5-things-must-know/">RAM Drive</a> for MySQL server.<br><br><br></div><div>thanks<br></div><div>Sutharsan Jeganathan<br></div></div><div id="DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #aaabb6">
<tr>
<td style="width:55px;padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/2016/icons/icon-envelope-open-tick-round-orange-v1.png"></a></td>
<td style="width:470px;padding-top:15px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" target="_blank" style="color:#4453ea">www.avast.com</a>
</td>
</tr>
</table><a href="#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 6, 2016 at 12:44 PM, Alan Lord <span dir="ltr"><<a href="mailto:alanslists@gmail.com" target="_blank">alanslists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We have a few systems with several million entity records (might be Contacts or Leads, or a vtlib designed custom entity module) and with many more than 100 users.<br>
<br>
There is one performance tweak I am aware of which I think will be going into 6.5 which adds a static cache to the to_html() function.<br>
<br>
<a href="http://code.vtiger.com/vtiger/vtigercrm/commit/ca51b56d04c0c335e7a7f8a7d25c2da7560e2a2c" rel="noreferrer" target="_blank">http://code.vtiger.com/vtiger/vtigercrm/commit/ca51b56d04c0c335e7a7f8a7d25c2da7560e2a2c</a><br>
<br>
We use the slow query log in MySQL (or MariaDB) to identify and then make judicious use of indexes to improve search performance.<br>
<br>
Install something like apc and/or memcached.<br>
<br>
If it's still slow, run it on the fastest h/w you can afford and use SSDs for storage.<br>
<br>
But on the whole it seems to work pretty well even with a considerable number of records. (Although I think 100,000,000 might be a struggle for this architecture!).<br>
<br>
HTH<br>
<br>
Al<br>
<br>
On 05/04/16 22:46, socialboostdk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone.<br>
<br>
I have a questions towards vtigers scalability.<br>
<br>
How many contacts would be realistic for me to have in a vtiger<br>
installation (latest stable version)?<br>
<br>
If we assume I will use some cloud hosting and scale that WAY up, and I<br>
will use the standard contact setup? I can probably deactivate most<br>
other modules<br>
<br>
I will actually access the data via the API, so the overhead of any<br>
browser-loading etc. can be ignored.<br>
<br>
What would be your (educated) guess? 100.000? 1.000.000? 10.000.000?<br>
<br>
And what would be the bottleneck / how can I improve on the performance?<br>
Basically I need 10-100.000.000 contacts possible :-D<br>
<br>
THANKS!!<br>
<br>
best,<br>
Chris.<br>
<br>
<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" rel="noreferrer" target="_blank">http://www.vtiger.com/</a><br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" rel="noreferrer" target="_blank">http://www.vtiger.com/</a><br>
</blockquote></div><br></div>