Performance issues in Maintaining Pricelist for different years!!

Hi Guys!

We have a requirement where in we need to maintain different Price List for each future year. So there will be a Price list for 2014, 2015, 2016 etc. They also want older Price List to be used based upon agreement setups. So in current year 2014 they can also use 2012 price list.

issue: we are concerned on performance issues.

for example there are 6 price list 2009, 2010, 2011, 2012, 2013, 2014 for each year. We cannot end date any price list at header level. So if we populate 2010 Price list in the order using agreements, would the Pricing engine check all the price list like 2009, 2011, 2012, 2013, 2014. As Price Engine is process records line by line should we worry about performance issues.