> That's why you really need to be more precise in the data structures > you are planning on using. This can change the results significantly. > > So no, I don't have any specific answers to your questions as you don't > provide any specific information in what you ask.
Yeah. Let me see if I can follow up with more concrete information sometime in future. I find performance tuning to be workload dependent and it is difficult to project without having all the details. > Well disk (and memory) usage can also be important so as it seems > InnoDB storage is "less efficient" this may actually degrade > performance. Until you are more concrete it's hard to say what will > work best for you. At this point I'm fairly convinced that this idea of vertical paritioning a table into column tables will degrade performance unless the workload is tailor-made for this. The cost of joins and index lookup/column data seems a bit too high for almost any scenario. Thanks for the prompt response. I'll follow up with you if I have more concrete details. Thanks Kyong > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=kimky...@fhda.edu > Inst. Web Programmer CMDBA 5.0 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
