Important: This page is using cookies (cookies). Using this website without turning off cookies in browser, means that you agree for using it.
Buy Now! Features Downloads

Earn with us!

If you would like to start earning money with vBET join to Affiliate Program.
Results 1 to 4 of 4

Thread: DB size

  1. #1
    Senior Member
    Join Date
    Nov 2009
    Posts
    168

    Default DB size

    Is it normal for your database to triple in size following the installation of vBET?

    I started out with a 1Gb DB, and now I'm looking at close to 3. While I understand that entire pages posts are being cached here, wouldn't it be more stable to have this done in a separate database outside of vB (like 2.x does)?

  2. #2
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    Yes - your DB will grow. Your content is multiplied 52 times (if you have all languages enabled), so it is hard to not grow

    Using same DB does NOT affects stability forum at all, because there is no query which uses other resources from vB. Also vBET 2.x also use same database.

    You can always disable some languages, or just disable cache for some languages if DB size is an issue for you. But as long as you have space on your drive the size of DB does not affect you - vBET is using indexes for all queries. There is one thing which you can be interested if your cache tables are really big - those are clearing strategies. For more details about those please go to Admin CP -> vBET -> Cache.

  3. #3
    Senior Member
    Join Date
    Nov 2009
    Posts
    168

    Default

    Thanks for the reply! That clears up those concerns.

    My final concern is with mysqldumps. If I run mysqldump via command line, is there any way I can exclude the vBET cache tables from being dumped? I'd rather not waste space backing up the cache

  4. #4
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    We are planning to support file cache. It would take much more space on hard drive, but get data without DB queries. We didn't start implementation of this yet.

    At this moment we are planning how configurable it should be and other details. We want it running for everyone - it means without necessary to install any additional caching engine.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •