I implemented my browsing mechanism as below:
vector of records as source (vectorRec),
input from user starting records (startRec)
input from user number of records to show from starting records (recToShow)
i have a loop like this
for (int i = 0 ; i < recToShow ; i++)
{
record = vectorRec.at(i+startRec); // get a record
record.decompress
plotData(record);
}
for (int i = 0 ; i < recToShow ; i++)
{
record = vectorRec.at(i+startRec); // get a record
record.decompress
plotData(record);
}
To copy to clipboard, switch view to plain text mode
I noticed that if my vector has lesser count say 30 000 records, I browse faster than i have 60 000 records ofcourse i kept my number of records to show constant at this tests.
It seems that the bottleneck would be the retrieving of records from my vectors, now if i have to implement some simple caching , i might just split up the records into vectors of 10 000 what do you think guys? will it help if i will split it up.
baray98
Bookmarks