• Advertisement
  • entries
    422
  • comments
    1540
  • views
    489673

Volume cranked to eleven...

Sign in to follow this  

113 views

Quote:
Nigel Tufnel: The numbers all go to eleven. Look, right across the board, eleven, eleven, eleven and...
Marty DiBergi: Oh, I see. And most amps go up to ten?
Nigel Tufnel: Exactly.
Marty DiBergi: Does that mean it's louder? Is it any louder?
Nigel Tufnel: Well, it's one louder, isn't it? It's not ten. You see, most blokes, you know, will be playing at ten. You're on ten here, all the way up, all the way up, all the way up, you're on ten on your guitar. Where can you go from there? Where?
Marty DiBergi: I don't know.
Nigel Tufnel: Nowhere. Exactly. What we do is, if we need that extra push over the cliff, you know what we do?
Marty DiBergi: Put it up to eleven.
Nigel Tufnel: Eleven. Exactly. One louder.
Marty DiBergi: Why don't you just make ten louder and make ten be the top number and make that a little louder?
Nigel Tufnel: [pause] These go to eleven.
I think a combination of 2 litres of coffee and the last-minute adrenalin rush have kicked in. Motivation is at an all-time high and I was up and working by 8am today [grin]

Gotta get this dissertation off to the printers by Wednesday. Hopefully have all the content complete today, leaving tommorrow for minor reformatting, re-numbering etc...

Dug into the Nvidia performance tools this morning - needed to include some profiling info in my write-up. I wish they'd answer my questions about the registered developer program [sad]. Been trying to get something - anything - from the NV developer relations people. Nothing, not even a simple "get lost, we dont want to talk to you".


I know they only want "proper" developers with published titles, but I figure that the amount of material I publish online as well as my general spamming of various forums must count for something. Would be nice to get a headstart on things - couldn't hurt them to let me (indirectly) promote NV stuff could it?


I was using the latest 85.x ForceWare drivers which worked fine for me. But NVPerfKit required instrumented 79.70 drivers. Downgraded as appropriate... pops up a message saying "Incompatable GPU, hardware counters disabled - contact Nvidia developer relations for help". As if I'm gonna waste time trying to get a response from Nvidia [rolleyes]. Bye-bye NVPerfKit - nice knowing you. Next up was NVPerfHUD - awesome tool. Could possibly rival PIX if it weren't NV-only. Thing is, I noticed the frame-rate kept on spiking. Every second or so it'd briefly pause:



Thought it was something to do with the instrumented 79.70 drivers, so rolled back to 78.01 as suggested on their page. Same problem.

I'll probably ditch NVPerfHUD and go back to 85.x drivers. They kindly plaster the availability of NVPerfHUD 85.x compatabilty for registered developers only. GRRRRRR [flaming]. Maybe if I wait a while they'll release them publicly and I'll be happy.

Might well see about updating the flowchart from my last journal entry later today/tomorrow. Needs a better example image...
Sign in to follow this  


3 Comments


Recommended Comments

ARe you sure it simply isn't bad data? I mean, it looks like the driver and CPU time plummet down to zero whenever the framerate rises, which is almost contradictory. In the merits of computer science, can't you label those pieces of data as anomalous, esp. since it is due to drivers?

Share this comment


Link to comment
Yeah, thats what I did for the report... [grin]

But I'm still curious as to why its showing this behaviour. But equally, I don't really have time to press the issue [headshake]

Jack

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement