maintenance?

[Thomas]

I'm very interested in purchasing your script, however, like everyone else posting here, I'm a cautious shopper. Will your application require any on-going or scheduled maintenance in order to operate properly and at peak performance? I'm not referring to the maintenance of the hosting machine, I'm actually talking about the scripts or MySQL dbs themselves. I've had some scripts in the past, both MySQL and flat-text dbs that reached a capacity limit (I'm guessing) and actually froze. Are there any known problems or maintenance issues we should plan for before implementing and advertising this application?

[mark]

Hello,

there are no maintenance problems that I'm aware of.
If you'll have extremely high traffic and thousands of banner clicks per day, it may require to handle it somehow - like backuping old data and freeing the corresponding table.
It happened with impressions before (when customer had few houndred thousands impressions) which slowed down the database. We solved this issue in version 1.3.1 ad now it saves data in much more efficient format.

Otherwise, it is load tested, and except having overloaded database there is no known performance issue.

I'd also like to say that if some problem with performance appear later, we will work on it and we'll solve it.

with regards,

mark

[Thomas]

you mentioned freeing up corresponding tables. how is this done? can it be acheived through the admin panel of the application? or would this have to be done manually somehow? I'm not as proficient in db administration as I'd like to be. we do however plan to have several hundred affiliates, and thousands of impressions daily.

[mark]

There is no function for this now, but it is no problem adding it, or giving you database script that you'll just execute.

But I don't expect you'll run into problems with too many db records.
It can only happen if you really have thusands of clicks (not impressions) daily.

Impressions are saved in very efficient wayand they do not require freeing the table.

with regards,

mark