[wp-hackers] MySQL: Union vs global table

[Eric Hendrix]

Agreed, updated as infrequently as daily. Either way your performance for
"millions of rows per blog" will take a serious hit - hope folks running
this are on their own server - not a particularly suitable situation for
VPS or otherwise, right?


On Thu, Feb 20, 2014 at 5:36 PM, Chloé Desoutter <
chloe.desoutter+wphackers at gmail.com> wrote:

> Hi Dino,
>
> Fake a materialized view (by a CREATE OR REPLACE TABLE x AS SELECT) as
> MySQL doesn't support them. Update it on a regular period. This will suck
> the less.
>
> Yours sincerely
>
>
> 2014-02-20 23:15 GMT+01:00 Dino Termini <dino at duechiacchiere.it>:
>
> > Hi list,
> >
> > I am working on a plugin that stores information in a table. In MU
> > environments, each blog will have its own instance of that table (just
> like
> > wp itself does for posts etc). Now, I am also being asked to provide a
> > "network view" of that information. I evidently have two choices: UNION
> ALL
> > on wp_*_mytable, or use a global table with blog_id. We may be talking
> > about millions of rows per blog. So the latter approach would affect
> > performance when analyzing the info for a given site (more frequent), I
> > assume.
> >
> > What would you do in this case?
> >
> > Thanks
> > Dino
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
*Eric A. Hendrix*
hendronix at gmail.com
(910) 644-8940

*"Non Timebo Mala"*