At Montag, 14. Oktober 2002 14:57 Alberto Ruiz Cristina wrote: > Hi all > > I am new to MySql and I am thinking about using it for managing a > database, which would have a approximated length of 500 Mb. It is formed > of vectors.
Greetingz, from my experiences with several Databases since the 1970ies efficiency - especially effiency of relational Databases - is primarily dependant on the design of your data and programs. It depends first of all what you want to do with the data, e.g. in addition to what data you have, how many updates and what kind of updates you are doing, how many queries and what kind of them do you expect, how many clients are simultanously accessing the database and what they are doing... Any paper or book about relational database design and it's tuning will probably help you, MySQL is not "special" in that regard. Then the next important step will be the tuning of your database together your applications (or under simulated load which represents your environment). This may require some changes in the layout of your data and tables too, but it comes secondary, because the major faults are often done in the design of the application algorithms together with the design of the database. A design flaw can degrade your performance by several order of magnitudes (and can be difficult to fix), while the basic database tuning thingamagics (like adding or dropping an index) are relative cheap to do later. > Trouble is that I am worried about the ability of > MySql to handle that amount of data. The amount of data is not a problem, but how you access and update the data might be. For example: if you want to cut a hyperplane or space-slice (sorry, don't know the exact english phrase for that) through your vector-world, which orientation will these hyperplanes have? Will it be normal to one of your dimensions etc. Just storing 500 MB of vector data might even be done best in a binary file without using any database at all, which is read (with appropriate locking) into virtual memory as one large matrix, processed and perhaps written out again. If your problem is fit for a relational database, then MySQL can do the job. If not, then other RDBS have the same problems with it, probably. Get my idea? Greetings Michael -- Michael Zimmermann (http://vegaa.de) --------------------------------------------------------------------- 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
