Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Ali Saidi
That's an excellent idea and yes, that seems like a good course of action. Ali On 23.01.2013 14:04, nathan binkert wrote: > With the new system, for this case, dumping a subset of stats would > not be all that difficult. If you're dumping that frequently, it > doesn't seem to be a huge bur

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread nathan binkert
With the new system, for this case, dumping a subset of stats would not be all that difficult. If you're dumping that frequently, it doesn't seem to be a huge burden to expect people to narrow down the subset of stats that they're interested in if they want speed. On Wed, Jan 23, 2013 at 11:59 AM

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Ali Saidi
Yes. Pretty much the question in my mind is how many people are dumping stats at a rate greater than once every 100k instructions? Thanks, Ali On 23.01.2013 11:53, Steve Reinhardt wrote: > Right, I'd say the main concern here is for people whose usage model > incorporates fairly frequent

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Steve Reinhardt
Right, I'd say the main concern here is for people whose usage model incorporates fairly frequent periodic stats dumps (who are probably more likely to want the SQL output anyway). Steve On Wed, Jan 23, 2013 at 9:27 AM, nathan binkert wrote: > It's worth making the point that this is only when

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread nathan binkert
It's worth making the point that this is only when dumping the stats. Stats collection hasn't changed. If performance of the dump is really a concern, I'm sure I can offer some suggestions to improve things. On Wed, Jan 23, 2013 at 9:22 AM, Andreas Hansson wrote: > Hi Steve, > > I occurs when on

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Andreas Hansson
Hi Steve, I occurs when only using the SQL output, i.e. old text only replaced with new SQL only. Adding text output to the latter unfortunately slows things down even more due to the additional formatting/formula evaluation etc. In a typical use-case the text formatting could be done after the s

Re: [gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Steve Reinhardt
Hi Andreas, Sorry I have not had time to look at your patches, but I fully support what you're doing in principle. One clarification about the slowdown: does this occur even when you use text output, or does it occur only when you use SQL? That is, will users who stick with text output be affect

[gem5-dev] New Python stats system with SQL backend

2013-01-23 Thread Andreas Hansson
Hi all, The short version: A week ago I posted a number of review requests that build on top of Nate's initial work to move the stats from C++ to Python. The reviews, request 1636 to 1647, has not gotten any comments so far, and I would like to know if people are generally happy with these pat