|
You know, no one should have to explain this to you idiots, but iBill can't seem to communicate with its webmasters so I'll take the liberty of explaining a very simple concept:
iBill has a MASTER database that accepts and proccesses transactions.
In order to keep the load on the master db low and quick, they replicate this database to a separate "stats" (CMI) server (or servers) so that webmasters, etc check their stats against this "backup" database.
If the transaction load is too high. it can take a while for the replication to take place. Transactions are still being processesed in real-time on the master server. Eventually they'll be replicated to the CMI database and show up in the stats.
DON'T FUCKING WORRY ABOUT IT!
Yes, iBill should really solve this problem, but it may not be easy - maybe they can't upgrade the master DB machine or easily modify the network structure to increase throughput.
[FWIW: I do not work for iBill or know anything about their data structure, but this is a very simple concept to understand. Most (if not all) processors, large affiliate programs, etc have this very same setup]
|