Jump to content

Recommended Posts

Does anyone know if there are DB size limitations within MYSQL?  I have gotten conflicting reports everywhere I have looked on the internet.  Can someone let me know if/what the limitations of MYSQL are in regards to size?  I have a database that is already getting very large after three months and I am concerned that maybe I should look into a different DB alternative.  Let me know if anyone can help me out.  Thanks in advance.

Link to comment
https://forums.phpfreaks.com/topic/59914-solved-mysql-db-size-limitation/
Share on other sites

So there really isn't a limit then?  I have an application that will have 1000 entries in the database per week.  No attachments.  Just entries consisting of about 10 columns or so worth of data.  I keep seeing this "4 GB limit" everywhere on the net.  Apparently that is no longer the case. 

 

My next question is in regards to simultaneous queries.  I currently utilize a hosted solution for my application and understand that I will not be able to have 200 people all submitting queries at the same time without creating cpu utilization problems.  That being said, have you ran into problems with too many people hitting a database simultaneously while using MYSQL?

I'd like to see where you've seen mysql supporting only 4gb.

 

If that were the case, there'd be no way they could successfully sell it on an enterprise level offering support, fyi.

 

200 concurrent connections is a stretch for a lot of database servers. I seriously doubt you'll need that many.

 

A bit more insight on what my MySQL database has handled...

 

I have an app which has a 64 thread Thread Pool. Each successful transaction in my application has 7 writes and 4 reads.

 

The MySQL database I have installed can process 46 of these transactions / second (according to my latest performance numbers)

 

Anyway, to get to the point, I don't think you'll be having issues using MySQL.

Right.

MyISAM is smaller in size, but great for searching (selecting). Please note MyISAM does table level locking, as apposed to InnoDB which supports a larger size and offers row level locking.

 

If you have a database that will be doing alot of updating / inserting, I would highly recommend you switch the engine to InnoDB

 

 

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.