That's a good question. I'm not sure what is the answer. I'll do some Googling and get back to you if I bump into an anything. You should email the people at iPage as they probably could help you..
This is something we are addressing at the moment..
Along with indexes you will see the introduction of a new database class which has caching on a per query functionality which will improve performance for large stores and stores with a lot of traffic...
This article explains how indexes increase performance quite nicely.
Thanks sparky. I'm surrently developing a iPage site for a client that will use osC....with a lot of customization..
We will be listing roughly 100,000 products, with 2.7 million different pricing options....and I'm wondering how osC is gonna hold up for this type of shop..
I take it that you will base the store on MS-2?.
If you take a look in current CVS you will see the start of the new DB class has been introduced..
It would be a very interesting excercise to see the performance difference on such a large store...
Ok. Yes, we will be using MS2..
I was hoping that introducing new indexes into the DB will help, as I am afraid to see what type of performance setbacks we are going to have...
How about some benchmarks to show case the new OSC cache?.
The easier solution is to install mysql 4.0 with query cache and with plenty of memory > 512mb..
You don't have to wait for ms3 either...
Thought I would privde an update. I made a mistake....there won't be 2.7 million different pricing entries in the DB.....THERE'S GONNA BE 90 MILLION..
....As scary as that is..
This post has been edited by.
: 16 March 2004, 23:48..
I read this on a forums earlier and have used this on my site. I'm no where near the size you suggest, but these will help..
Alter table categories add index (sort_order);.
Alter table customers add index (customers_email_address);.
Alter table orders add index (customers_id);.
Alter table products add index (products_model), add index (products_price), add index (products_date_available), add index (manufacturers_id);.
Alter table products_attributes add index (products_id), add index (options_id);.
Alter table products_options add index (products_options_name);..
So if I use this command, will it index the model, price, date_available, and manufacturers id all together or serperately?.
I main index I'm worried about (in the table with 90 Million + entries) is gonna be customer_id, product_id, product_type_id, product_price .... and I'd like to index the customer_id, product_id, and product_type_id all together..
Was looking through the database structure, and I really don't see many indexes. Was wondering why more aren't used, and if the use of DB indexing will be implemented more in MS3..
As I don't know really very much about databases I'm just courious how an index would affect a shopscript?.
I mean data access is pretty straight forward..
You don't need to search, really..