Re: [WebDNA] Use of MySQL with WebDNA
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105821
interpreted = N
texte = One client I help sometimes has a 500+ MB webdna db.. with no problems at all. But it does not get written to more than 10-15 times a day... and read from less than a 1,000 times a day, probably. All my clients are running in shared host environments. I wonder how webdna7/VPS changes the landscape. -G On Sep 28, 2010, at 9:45 AM, Toby Cox wrote: > I hadn't thought of this, but now that I think of it we also have a > problem with large, heavy traffic, heavy write DBs > > On an ecommerce site we run, one particular db currently stands at > 58,000 records (just over 1Mb) and it has started to corrupt records > in the last 4-6 months. Obviously this is something that tends not > to happen with MySQL. > > High traffic large databases with little writing do just fine, as do > high traffic smaller DBs with lots of writing. We have a record of > all dispatched items that gets written to just a few hundred times a > day. This stands at 167,000 records and 1.2Mb and is just fine. > > Meanwhile, with CakePHP and MySQL we have large DBs (250,000+) that > are written to 1,000+ times per day with no corruption. > > It's a problem that we can handle at the moment, by occasionally > running a first aid script, but I can't imagine that in 6-12 months > we are going to be running WebDNA in the same format as we do now. > > > > TC
Associated Messages, from the most recent to the oldest:
One client I help sometimes has a 500+ MB webdna db.. with no problems at all. But it does not get written to more than 10-15 times a day... and read from less than a 1,000 times a day, probably. All my clients are running in shared host environments. I wonder how webdna7/VPS changes the landscape. -G On Sep 28, 2010, at 9:45 AM, Toby Cox wrote: > I hadn't thought of this, but now that I think of it we also have a > problem with large, heavy traffic, heavy write DBs > > On an ecommerce site we run, one particular db currently stands at > 58,000 records (just over 1Mb) and it has started to corrupt records > in the last 4-6 months. Obviously this is something that tends not > to happen with MySQL. > > High traffic large databases with little writing do just fine, as do > high traffic smaller DBs with lots of writing. We have a record of > all dispatched items that gets written to just a few hundred times a > day. This stands at 167,000 records and 1.2Mb and is just fine. > > Meanwhile, with CakePHP and MySQL we have large DBs (250,000+) that > are written to 1,000+ times per day with no corruption. > > It's a problem that we can handle at the moment, by occasionally > running a first aid script, but I can't imagine that in 6-12 months > we are going to be running WebDNA in the same format as we do now. > > > > TC
Govinda
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
MATH PROBLEM (1997)
Sku numbers (1997)
4.0 upgrade and existing webMerchant (2000)
ImageMap (1997)
Date Formats (1997)
Slow Code, how to speed up (2002)
PCS Frames (1997)
Mass Mail (2000)
Error: Too many nested [xxx] contexts (1997)
Version f1 status (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
RE: Error: template (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
Security Question (1997)
Revisit: speed test (2002)
Logical and or in [hideif] (1997)
Catalogs and W* (1996)
[TaxableTotal] - not working with AOL and IE (1997)
Problem getting shipping to calculate (2003)
Re:2nd WebCatalog2 Feature Request (1996)