mysql can manage a large amount of records bisan pila pa na ka thousands. taronga lang ug manage ang inyo db para dali ra e query. dapat gamit ka ug index, reference, relationship para wlay field na magbalik balik ug declare. payts....
mysql can manage a large amount of records bisan pila pa na ka thousands. taronga lang ug manage ang inyo db para dali ra e query. dapat gamit ka ug index, reference, relationship para wlay field na magbalik balik ug declare. payts....
proper normalization and indexing and you'll be fine. one db i'm maintaining has 32 million records across 38 tables (so it's a fairly small app). it gets ~500k queries per hour but the average resource load of the server isn't even 10% at peak times. besides, you can always scale the hardware and do load sharing inig abot sa panahon if you do hit MySQL's limits. pero dako na siguro kaayo imong company ana
gamit pud ug slow_query_log, EXPLAIN, etc during development so you can benchmark and optimize your queries.
I'll just add something ha..
1. You can't query a picture but you can store the filenames and you can do a query with the stored filenames. In websites that operates in Mysql and displays images, its not the MySQL that is making it slow but the caching of the images.
2. If you have 10 million records, there will be no sense to query and display that helluva lot of records at one.
3. There are procedures to maximize your database performance. Database design is one.
Indexing lang....primary keys
para sa ako lang.. dili nindot if ang image iapil ug store sa database na pwede man sa directory nalang e save... basta taronga lang ug manage ang imo database.
Question ko lang.. unsaon pag connect sa MySQL gamit ako program vb6 pinaagi sa ako public IP... ng.libog kaau ko kay dili ko ka connect kng LAN lang maka connect man ko?
please help... tnx
Performance wise, do not store pictures on your mysql database, instead store it into a directory... Then store its filename and/or its location to a table, query these info and have your program point to the file location.
Database performance depends on your design and structure (either MS-SQL, MySQL, PostGre SQL, etc)...
Sa amo, we have been dealing with "Table Locking" issues due to design flaws (gibyaan sa mga developer nga nagkalitse-litse ang system) sa database (esp. union select queries), which led us to redesign and restructure our database (MySQL 5.0)...
Security purposes, ayaw ipa dretso ug connect imo clients sa imo public ip bro (either you change your machine's ip to public IPs)... Use port forwarding instead, and forward any PORT 3306 request to your local database machine.
By doing that, dili directly expose imo machine to outside network... and besides, you can still give "user"@"localhost" privilege sa tanang connections nimo, bsan pa ug outside your local area network...
Kay kon imo na ipaconnect ang outside network nimo, you have to give privileges to "user"@"%", that means tanan source requests, iya dawaton...
Similar Threads |
|