innodb and vbulletin 1.1
Hello, I have a few questions. First I work on a very high traffic site that uses vbulletin 1.1 to run its bb. The bb is very high traffic around 60-200 concurrent users. We are starting to run into some serious locking issues, and I am thinking about converting the high use tables(maby all) to innodb. My first question is will this break anything in the application layer? Second we may be moving this to a new serve where I could have 6+ disks. I have done some testing and found that after all the importing into innodb all the data is around 1gb. Would it be helpful to add these extra disks creating 1+gb raw partition on each one to spread the io across the disks and controllers. And how does innodb distribute the data through the table spaces? Thanks for any help Byron [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Server Problems
You may want to check your /tmp partion. it may be creating some temp tables. -t, --tmpdir=path Path for temporary files. It may be useful if your default /tmp directory resides on a partition too small to hold temporary tables. Byron [EMAIL PROTECTED] wrote: Hello All, Background: -Site has 8000 uniques per day, average of 300 online at once hammering the forums. -POST table has over 350,000 entries When doing a backup with mysqldump and then trying to re-import the data to a test server, we keep getting: ERROR 1030 at line 207477: Got error 28 from table handler - No space left on device Is there an way to remedy this problem? Obviously we have a setup error or something as there is a 20gig drive in the mySQL server. mysql database Mike(mickalo)Blezien =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Thunder Rain Internet Publishing Providing Internet Solutions that work! http://www.thunder-rain.com Tel: 1(225)686-2002 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
thread_cache_size on linux
I am trying to tune mysql on linux for a web based application. Reading throw the docs I found thread_cache_size I checked what it was set to by default and found that it was 0. In the docs it says That it doesn't make much difference if you have a good thread implementation. So my major question is does linux have a good thread implementations and ether way will this make a difference? The only reason That I am kinda hesitant to set this up really high is that it would keep the threads living for a long time witch may cause memory leaks. I would appreciate any help and also if any one has good links other than the manual for tuning mysql. Thanks Byron - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
