Jump to content

Recommended Posts

What would you call a cluttered table that could effect performance

 

100,000 rows of data accumulating 20MB in total, the table structure has 30 fields but the field content is 1 or 0

 

Or

 

100,000 rows of data accumulating 50MB in total, the table structure has 10 fields but the field content usernames

 

 

Im just wondering whether it will cause a problem having a ton of fields in a table, or would it be better to split it into 3 tables and just join..

 

Join has its overhead, but so does having 30 fields as apposed to 10

 

Or perhabs fields in a row do not cause any problems at all, rather, the number of rows are what to be carefull with aswell as the content (numbers vrs words)

 

Any advice on this

Link to comment
https://forums.phpfreaks.com/topic/85336-solved-fields/
Share on other sites

Obviously, they can't be normalized the same way... size of a record is really in issue here, determines number held in various buffers, which determines how fast mysql can perform many operations -- which is why it's bad to have BLOB/TEXT fields mixed in with other data types in general.

Link to comment
https://forums.phpfreaks.com/topic/85336-solved-fields/#findComment-435581
Share on other sites

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.