Subash,
If that GPU resource warning issue actually only came in for machines with low-level GPU/s it would be understandable. Mine is an EVGA packaged nVidia GTX770 with 4 gigabytes of vRAM and 1536 CUDA cores. Used on an i7 4-physical core CPU machine.
A GTX770/4Gb-vRAM/1536 CUDA core graphics card isn't particularly ... shabby? ... it would seem?
Now, though my machine tests great with other tools, GPUZ does note that none of the Adobe DVA's fully utilize my card even when invoking effects that are heavy users of GPU/CUDA. I never go much past a gig of that 4 gigs of vRAM used within the Adobe apps, while other things can quickly grab all of it ... and haven't so far diagnosed why. GPU usage itself stays down around 6% ... no matter the workload. I have been putting off running the PBM benchtest which I probably need to get to ... but I'm working again albeit not totally screaming along. So I've not taken the time.
When the December release came out, my use of Sg simply stopped for any DL work. Then later on one day, it started working again mostly sort of, as noted online here, though neither my builder nor I have any idea why. So it's an intriguing puzzle for the team: why do the Adobe DVA's sometimes choose not to utilize entirely functional video card capability? For many of the responders on this and other threads here and other places I haunt, the people with this problem had cards that were as or even far more capable than mine ... and rather mystified at being told some fancy new high-powered video card was "insufficient".
But it was ONLY "insufficient" in a DL process. Native, the app sees the cards. DL, there were insufficient video resources. Huh.
Neil