ILoveHostasaurus
04-04-06, 10:12 PM
Is anyone here using the built-in affiliate system in MM5? We have a customer whose store packs incredibly slowly, usually timing out even with a timeout value of five minutes. It's Merchant 5 running on mivasql, not MySQL, and is not terribly large, all of its databases together amount to 62 MB of data. The one unique characteristic of this store is that it's not only mivasql but is also running the built-in affiliate program which most users of Merchant do not use due to the issues with it.
While running a program debugger against the store during a pack, I found that there was a gap of a full two and a half minutes between when Merchant opened a new temporary file mivadata/s05_AffiliateSession00000003 and when it finished with that and moved on to opening mivadata/Merchant5/s05/attributetemplates.dbf. The store does not actually have five stores, just one but it had been added and removed a few times during development so the storefront counter got up to 5. So obviously the problem lies somewhere in the affiliate code; maybe MM5 still has the same issue with the affiliates database accumulating records that never go away? The affiliates database on the site is up to more than 40,000 records even though it is not heavily affiliate driven nor does it do a huge amount of traffic. I don't want to clear that database since it may be in active use to track referrals for the site unless someone can confirm that revenue tracking is not actually dependent on that database.
Any input or suggestions would be appreciated.
While running a program debugger against the store during a pack, I found that there was a gap of a full two and a half minutes between when Merchant opened a new temporary file mivadata/s05_AffiliateSession00000003 and when it finished with that and moved on to opening mivadata/Merchant5/s05/attributetemplates.dbf. The store does not actually have five stores, just one but it had been added and removed a few times during development so the storefront counter got up to 5. So obviously the problem lies somewhere in the affiliate code; maybe MM5 still has the same issue with the affiliates database accumulating records that never go away? The affiliates database on the site is up to more than 40,000 records even though it is not heavily affiliate driven nor does it do a huge amount of traffic. I don't want to clear that database since it may be in active use to track referrals for the site unless someone can confirm that revenue tracking is not actually dependent on that database.
Any input or suggestions would be appreciated.