Jump to content
  • 0

WHMCS - Database Size


acenetryan

Question

Hello All,

 

We're currently running a Modernbill and Kayako solution for our billing and support. With the release of Plesk Billing v6, we've decided to start shopping around before taking the plunge and noticed that WHMCS seems to be a rather complete package.

 

One of the major concerns I have with a software that is as complete as this is how it will operate on top of a large database. I was wondering how large everyone's installs are and what type of hardware specs you need to achieve reasonable speed from the software.

 

Just to give you an idea of our past, we used InverseFlow back in the day and posting to tickets with a subsequent refresh of the helpdesk would often take 10-12 seconds once our database started getting large (on the order of tens of thousands of records). Suffice it to say our table size for our tickets

is much larger today and Kayako seems to do a nice job of handling it.

 

With regards to our ModernBill performance, we had a Dual Xeon 3.0 with 2 GB of RAM which essentially served nothing but our Modernbill install. With the size of our database, we ended up waiting anywhere from 5-10 seconds depending on the query. We've since moved our install to newer, more powerful hardware.

 

What this all boils down to is:

 

-- What hardware are you using to run WHMCS?

-- How many tickets in your DB?

-- How many clients/invoices?

-- Typical Load Time for Helpdesk?

-- Typical Load Time for Billing Queries?

 

Thanks in advance.

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

We had the same software setup, and now use WHMCS/Kayako. I'm fine with Kayako's speed, but MB was awful. WHMCS is great, extremely fast. The database is also around 10% of the size of the MB database, with all of the same customers/packages/invoices/etc.

Link to comment
Share on other sites

  • 0
We had the same software setup, and now use WHMCS/Kayako. I'm fine with Kayako's speed, but MB was awful. WHMCS is great, extremely fast. The database is also around 10% of the size of the MB database, with all of the same customers/packages/invoices/etc.

 

Wow, that is impressive. I have to agree, Kayako's speed is more than adequate. I notice that it seems to be popular to keep the installation of Kayako along side WHMCS. keliix06, care to elaborate why you choose to do this in particular? From what I can see WHMCS seems to be quite complete even as a ticket system. Is there some must-have functionality that Kayako provides that is not within WHMCS?

Link to comment
Share on other sites

  • 0

We use LiveResponse, so that was one reason. We could easily switch to something live LiveZilla, so that certainly wasn't a big concern.

 

Really, it's we have 5 years of ticket data in Kayako. We're used to it, customers are used to it and seem to like it. We have a number of departments and use several custom fields. We didn't look too deeply into the WHMCS support module, but I wouldn't expect it could do everything we needed.

 

The way I see it is WHMCS is built for billing and Kayako is built for support. Let them do what they were built to do. The integration works perfectly, so the clients have no idea they are in 2 different systems.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated