Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!
We have tried Mint previously but it spanked the CPU with the amount of traffic we had at the time. We are currently using Hitslink but are having problems with the external js so want to keep it in all in-house.
If anyway has a site with the same traffic and uses Mint 2 we’d like to know how you are finding it?
Thanks for your help.
If it becomes too much of a problem, you could always keep the database size low…
Mint has an option where you can specify how big you’ll allow the Mint database to get, before it starts deleting entries and whatnot.
I think the main problem with Mint 1 was inserting to the db not reading back for our purposes.
exactly, the stored amount inside the database doesn’t matters.
Are you talking about unique visits or total hits?
1 million hits per month should be one hit every ~3 seconds.
Mint should be able to handle this : )
Don’t forget to raise the “visit table size”-setting!
Mint 1 and Mint 2 both handle page views of greater than that quantity for my web site. If that kind of traffic (which is not really that much) is “spanking” your CPU, then you’re using insufficient hardware or else your database is not properly tuned. I did have to move my DB to a second hosting provider, since my first one felt the traffic-tracking was a violation of terms of service, but that’s unrelated to Mint. So you might consider that: use a server for the DB that is different from your httpd server.
Thanks for the insight Grant.
My only addition would be, I would strongly recommend against Till’s suggestion of raising your max database size if you do that much traffic. Mint runs best at the default 25-30 MB—especially if your database server is on the slow side.
Where’s the database size pref gone, btw? I don’t see it anymore in Mint 2.
Absolutely. If you start hitting even higher traffic than this, Grant’s suggestion about another box works just fine. Just went did this a few days ago. We love mint and use it so much (we make our own internal pepper too) that we just gave it a big part of its own box, along with data backups and a few other smaller, internal services.
TheBends, the database size option has been hidden in Mint 2.0
To view and or change you must add a query command to your mint url. your url will look something like this:
http://yourdomain.com/mint/?preferences&advanced
You got the URL wrong (just found it)
it’s yourdomain.com/mint/?preferences&advanced
BTW: My Mint runs since 2005. I can only see “Past Year” data for 2006, though. Is it possible to get data from 2005?
Also: What does “Remove visit data more than x week” mean? Which data is deleted exactly?
What happens when the DB is kept small, i.e. 15 MB?
Thanks everyone - it is 1 million pages served - not hits. Not Amazon I know but we’re happy with it :)
Yes we do now have a seperate db box now so that may help the cause - everything was running from the one box when we tried Mint 1.
I just didn’t want to spend the money again and find nothing had changed but if there’s people running it succesfully on higher traffic sites then that is great to hear.
I guess my only concern is having to continually trim the db. The thing I like about Hitslink is being able to see back a year or two and do some comparisons on the fly.
In terms of what Mint allows you to see, what happens when entries become deleted?
Does it affect any of the cumulative totals?
Obviously some of the peppers only apply to a limited time period anyways (e.g. trends), but what effect does the expiration of data have on peppers that make no mention of time period- like Searches?
Also, some of the peppers have time periods up to a year long- so is it safe to assume that some cumulative totals are kept regardless of entries being deleted?
Let’s assume I had a super beefy database server and virtually limitless storage- would there be any advantages to saving entries further back in time since Mint doesn’t let you generate reports for arbitrary periods of time?
Does it affect any of the cumulative totals?
No, these values are stored seperately.
would there be any advantages to saving entries further back in time since Mint doesn’t let you generate reports for arbitrary periods of time?
Not really no, Mint really isn’t a stat archiving tools. Its more of a whats new and happening (“fresh view”) of your site.
The default database values are a good basis.
That said, like you mentioned some Pepper may or may not be more useful if older data is stored. Undecided.
You must be logged in to reply. Login above or create an account
