Hi, I think you need to decide yourself which way you want to go. Both have advantages and disadvantages.
Regards, Thomas On Wed, Dec 4, 2013 at 2:19 AM, James Chan <[email protected]> wrote: > Hi Thomas, > > What I'm trying to create is a web application. > There will be more than 100 users, every users has his/her own 50 tables > with simple schema and frequent queries. > Since users' data are indenpendent, maybe I can create a db for each user, > that means more than 100 databases. > Originally the total data size would be 1~2TB in one db, now each db size > will reduce to 10~20G. > > But working in this way, it will consume very much memory when many users > connect in simultaneously. > And frequent open-close databases will impact the performance, right? > > > BR, > James > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
