If you have been looking at the Service thread last week, you may have noticed that we performed a website maintenance on Wednesday night. The purpose of this maintenance was to archive some of the data which was used on the "My Recruits" page.
We had already limited the display of data on this page to two Payback periods (the current period, and the last complete period), what we did last week was to archive some of the data which was too old to be displayed.
We have been working on archiving data on this page for two reasons:
- to improve performance: If there are a lot of data to go through, the page takes much longer to load and slows down the whole website. We are also looking at other clever database tricks to improve the performance.
- to free some valuable storage space: Archiving unused data helps us stay lean
Archiving the data on the "My Recruits" page is only one step of the work we are doing to improve the reliability and performance of the website.
We are now looking ahead and are planning to do a similar operation on the "My orders" page. The current plan is to archive the data which is older than the 01/11/2013. We are looking at doing this on the night of the 25/02 but we may adjust this date as we refine the details.
This will allow us to archive a significant amount of data, while keeping a lot of orders available to the members.
To help you measure the impact of this change, only 11% of members coming to this page are looking further than the last 5 transactions, much less to anything which is more than a few months old. Keeping more than one year of data available would cover this need.
If you like to keep a very tight record of your operations, we advise to make a copy of your oldest orders ahead of the 25/02.
Records of older top-ups, goodybag purchases and payback payments will still be available to the agents after the orders have been archived. Please make sure to communicate the date and the details of the order you are asking for so they can find it for you.
I think we found the right balance between performance and accessibility of the information but I'd like to hear from you if you think that we missed something.
Thank you for your help,