Background Paragraph: Storing large volumes of data – When storing XML to either file or database, the volume of data a system produces can often exceed reasonable limits, with a number of detriments: the access times go up as more data is read, CPU load goes up as XML data takes more power to process, and storage costs go up. By storing XML data in Fast Infoset format, data volume may be reduced by as much as 80 percent. 
Story: Bob works for a data storage company. He has now three projects, project A, project B, and project C, simultaneously going on. All of them involves storing 
XML data. Project A has small volume of data, but project B and project C has large volume of data. He applied Fast Infoset format for project B, but didn't apply that format for project C.
Which project would have higher access times, project A or project C? Which project would have lower access times, project A or project C? Which project would register higher CPU load, project A or project C? Which project would register lower CPU load, project A or project C? Will project A incur higher or lower storage cost than porject C? Will project C incur higher or lower storage cost than porject A? Would project A have higher or lower access times compared to project C? Would project B have reduced or enlarged data volume than porject C? Would project C have higher or lower access times compared to project A? Would project C have reduced or enlarged data volume than porject B?