 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
I have "downgraded" my graphics adapter to a Nvidia GT630, because I want to see if more memory will speed up the work in the editor.
The GT630 has 4GB memory.
I have also installed GPU-Z to monitor what is happening.
But I cannot understand the result. The wheel shown in the printscreen below is spinning and spinning and spinning even though the GPU load are only 19% and memory used is only 752MB out of 4000MB.
What is the APG editor doing while the wheel is spinning ???????
leifs
Offline
It is like some programms that use not all cores that you have in your CPU and therefore not reaching 100%. This because they were not programmed to use multiple/cores or because the task to be done cannot logically be split.
A GPU has many 'cores' and Kolor programmed APG very smart to be able to use the GPU as best as possible. But there are limits to what can be done, often because of the logic of the algorithm used.
Don't worry, I sometimes notice 0%, other times 46% (of a 600MHZ clock). I am just happy the preview is faster then it was and that is here at all in the first place.
Last edited by HansKeesom (2012-10-05 22:58:03)
Offline
I do worry. My other card is a ATI HD6850 and it gave me a Windows rating at 7.2. It had only 1 GB memory though (I have 3 monitors).
Now I have 4GB and a windows rating of 6.5 and the wheel is spinning and spinning.
To me it seems that there is no gain at all in APG adding memory to the GPU.
leifs
Last edited by leifs (2012-10-05 23:36:52)
Offline
I have an idea of what is going on:
even though I'm only looking at at a small part of the pano APG editor is "rendering all over the place", using a lot of time on parts I'm not seeing.
it's not like the "krpano approach": rendering only the part I'm looking at.
correct me if I'm wrong.
If this is the case Kolor should have a look at this, as the editor is becoming more important. Stitching errors should be identified and corrected before rendering instead of after hours of rendering.
leifs
Offline
I was wrong. When the whole pano, 360x180 is shown, the wheel is spinning and spinning also.
And it is blocking the use of moving the pano/slowing the use of the editor.
I would still want to know how to speed up the editor/remove the wait for the spinning wheel.
leifs
Offline
leifs wrote:
I would still want to know how to speed up the editor/remove the wait for the spinning wheel.
Guess you´re talking about APG 3 Beta1 - well it´s a Beta1 . . . 
Just give Kolor some more time to get it straight.
best, Klaus
Offline
... and if you used autopano 3.0 alpha x version than sorry ... gpu was not working/enabled
Offline
leifs wrote:
I do worry. My other card is a ATI HD6850 and it gave me a Windows rating at 7.2. It had only 1 GB memory though (I have 3 monitors).
Now I have 4GB and a windows rating of 6.5 and the wheel is spinning and spinning.
To me it seems that there is no gain at all in APG adding memory to the GPU.
leifs
If you use the windows rating to evaluate your GPU-card, I think you are being a bit unfair to the cards. There are better test for GPU-cards.
As discussed with AlexandreJ in other threads, memory is important. It allows APG to store all informations about a pano in the GPU memory so it can work. I had a 512 MB card before and often saw the card could only hold 1/4 of what APG would like it to hold. Now I have a 85 euro card with 4 GB on it an the editor really flies and can hold much larger panoramas.
Yes APG might have some possibilities for improvement on using the APG, we are all looking forward to it.
Offline
The spinning wheel is a known bug: issue 1509
Offline
