<p>Lowering some mysql options helps as well. However, if you are going to use this server for mysql and can give it more than 2gb then 64bits is your way.</p>
<p>Regards, Ruslan. From phone.</p>
<div class="gmail_quote">05.05.2011 3:13 пользователь "Alex Vandiver" <<a href="mailto:alexmv@bestpractical.com">alexmv@bestpractical.com</a>> написал:<br type="attribution">> On Wed, 2011-05-04 at 14:06 -0700, Jeff Albert wrote:<br>
>> Thanks for the quick reply. MySQL's error log suggests it's failing to<br>>> allocate memory past about 2.5GB; I'll work with our DBAs to see what<br>>> we can do with MySQL in this area.<br>
> <br>> This is likely because you're running a 32-bit kernel, and MySQL is<br>> unable to access more memory because of that. Running a 64-bit kernel<br>> will allow you to allocate more memory to MySQL.<br>
> <br>>> Generally I'm curious about the feasibility of continuing to run a<br>>> single large instance of RT; presumably at some point the query times<br>>> will just become untenable (bringing up the query builder in our<br>
>> existing 3.4 instance can take up to a minute even now). Would you<br>>> recommend separating into smaller instances, or a different approach?<br>> <br>> There are existing RT instances with terabytes of data. Proper tuning,<br>
> indexing, and provisioning of your database will go a long way.<br>> - Alex<br>> <br>> _______________________________________________<br>> List info: <a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel</a><br>
</div>