Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor QTC Integration Items #4

Open
kspaff opened this issue Mar 2, 2012 · 8 comments
Open

Minor QTC Integration Items #4

kspaff opened this issue Mar 2, 2012 · 8 comments
Assignees

Comments

@kspaff
Copy link
Contributor

kspaff commented Mar 2, 2012

Testing issue tracker with a couple of minor action items for QTC integration.

@adanalis should check and make sure:

  • What I put on the wiki page (https://github.com/spaffy/shoc/wiki/Qtc) looks correct and maybe add the outputs. I haven't run QTC yet to see what metric the result is.
  • Move QTC to Level 2 directory
  • Add the -s parameter and sizes, then I will integrate into driver script and google results db
@ghost ghost assigned adanalis Mar 2, 2012
@rothpc
Copy link
Contributor

rothpc commented May 10, 2012

Commit 18925dc moves QTC to level 2.

@rothpc
Copy link
Contributor

rothpc commented May 10, 2012

Commit 1b83eb7 integrates QTC into driver script

@kspaff
Copy link
Contributor Author

kspaff commented Jun 6, 2012

@adanalis QTC problem sizes need a little adjustment. -s 4 took 81 minutes on the Kepler in newark.

@kspaff
Copy link
Contributor Author

kspaff commented Jun 6, 2012

Also, the only difference I notice in the output is that the Kepler (gtx680) is allocating much less texture memory (193MB vs. 1024MB on the Tesla M2090 in Keeneland)

@adanalis
Copy link

adanalis commented Jun 6, 2012

This is because "-s 4" is supposed to be badass :-)

On Jun 6, 2012, at 10:22 AM, Kyle Spafford wrote:

@adanalis QTC problem sizes need a little adjustment. -s 4 took 81 minutes on the Kepler in newark.


Reply to this email directly or view it on GitHub:
https://github.com/spaffy/shoc/issues/4#issuecomment-6151762

@rothpc
Copy link
Contributor

rothpc commented Jun 6, 2012

I don't think it takes that long on a M2090, so this seems to be a problem with the mapping of qtc to kepler.

On Jun 6, 2012, at 11:08 , adanalis wrote:

This is because "-s 4" is supposed to be badass :-)

On Jun 6, 2012, at 10:22 AM, Kyle Spafford wrote:

@adanalis QTC problem sizes need a little adjustment. -s 4 took 81 minutes on the Kepler in newark.


Reply to this email directly or view it on GitHub:
https://github.com/spaffy/shoc/issues/4#issuecomment-6151762


Reply to this email directly or view it on GitHub:
https://github.com/spaffy/shoc/issues/4#issuecomment-6153097

Philip C. Roth | +1 865 241-1543 | http://ft.ornl.gov/~rothpc

@kspaff
Copy link
Contributor Author

kspaff commented Jun 6, 2012

Yeah, total runtime on 1 M2090 GPU on Keeneland is only ~68 seconds, so the slowdown is quite surprising.

@adanalis
Copy link

adanalis commented Jun 6, 2012

It's probably interesting to tune it. There are a couple of parameters that are easily tunable and should have a large effect on performance (i.e. number of threads/TB and numbers of registers per thread). I will look into it.

A.

On Jun 6, 2012, at 11:27 AM, Kyle Spafford wrote:

Yeah, total runtime on 1 M2090 GPU on Keeneland is only ~68 seconds, so the slowdown is quite surprising.


Reply to this email directly or view it on GitHub:
https://github.com/spaffy/shoc/issues/4#issuecomment-6153599

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants