-
Notifications
You must be signed in to change notification settings - Fork 104
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
Comments
Commit 18925dc moves QTC to level 2. |
Commit 1b83eb7 integrates QTC into driver script |
@adanalis QTC problem sizes need a little adjustment. -s 4 took 81 minutes on the Kepler in newark. |
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) |
This is because "-s 4" is supposed to be badass :-) On Jun 6, 2012, at 10:22 AM, Kyle Spafford wrote:
|
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:
Philip C. Roth | +1 865 241-1543 | http://ft.ornl.gov/~rothpc |
Yeah, total runtime on 1 M2090 GPU on Keeneland is only ~68 seconds, so the slowdown is quite surprising. |
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:
|
Testing issue tracker with a couple of minor action items for QTC integration.
@adanalis should check and make sure:
The text was updated successfully, but these errors were encountered: