Hi I've created an app with a background task but I can't figure out how to profiling (memory and cpu) I've already tried this link http://msdn.microsoft.com/en-us/library/windows/apps/dn641982.aspx but only works with foreground app...
My needs is to profiling cpu and memory
thanks
You could try the Performance Monitor / Performance Recorder that comes with Visual Studio. Details here: http://msdn.microsoft.com/en-us/library/windows/apps/dn629255.aspx
Related
I have recently installed a xamarin android player for developing android application but after the complete installation when i open a xamarin android player it will throw a following error...
****xamarin android player failed to initialize device vboxmanag****
Can anyone help me or tell me what can I do.
I am running Windows 10 Pro and use Oracle VBox v.5.0.4.
if your case same with me : first, you need to uninstall the current version of Oracle VBox then install the new version that already support Windows 10. i use v. 5.1. You can download it here
then, just try to re-launch the emulator.
I found some info by Googling around that may help starting a device in the Android Player. I have Vers 0.6.5 of the player.
Open VirtualBox directly as suggested by Cook Data. You will get the REAL error message which may related to vt-ix....
Make sure that the the bios has enabled the virtual technology aka vt-ix. Just do a reboot and you should find it in he bios setup - maybe under advanced. AMD and INTEL have slightly different names for it.
Reduce the system memory for the device you wish to start to 1024 Mb if it is currently 2048 Mb
I also got a warning about video memory which I increased to 10Mb from 8Mb
My setup runs over Hyper-V which has its own foibles so YMMV and I only started on this stuff today...
For Windows 10 users
(After Bios Virtualization enabled)
Use VirtualBox 5.1.14
https://www.virtualbox.org/wiki/Downloads
I have a single GPU in my Windows 7 system. Would like to debug my gpu code locally on this machine.
There is a confusion regarding this. Do I need to do headless debugging, (may be making my on-board display as display driver), as explained in Setup Local Headless GPU Debugging?
Or do I need not do any thing like that?
You cannot do local headless debugging with only a single GPU. Headless means there is no monitor or active display attached to the GPU that is running the code under debug. If you are debugging locally, you need this display to see the nsight GUI and your windows desktop.
Single GPU local (non-headless) debugging is covered in the nsight manual.
If you can enable another GPU (need not be an NVIDIA GPU), then you can use that GPU for your windows display, and do headless debugging on the NVIDIA GPU.
After I updated my Samsung Series 9 SSD laptop with 8GB of RAM to Windows 8.1, (not even a year old, and top-of-line when purchased last november), I am now unable to run the Windows Phone emulator while debugging my WP8 app.
The error messages I see is:
"Not enough memory in the system to start the virtual machine emulator
WVGA 512MB.user with ram size 512 megabytes"
Well, the instant I attempt to run a build, it the machine immediately goes from 25% memory consumed to 80% consumed. Even after I close Visual Studio Express 2012, still it is stuck at 80% memory consumption according to the task manager. At this point, I am unable to run the Windows Phone emulator to test my app.
How can I work around this issue without replacing my hardware?
Thanks!
Microsoft has now posted a KB article with information about how to edit the registry to correct this:
Start Registry Editor.
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Virtualization
Right-click the Virtualization
folder, point to New, and then click DWORD Value.
Type MemoryReserve, and then press Enter.
Double-click MemoryReserve,
enter 2048 in the Value data box, select the Decimal option, and
then click OK.
Close Registry Editor.
I can't post comments yet but I wanted to confirm being able to start the emulator after starting the Hyper-V Manager. I was getting memory errors trying to launch the emulator; I started the emulator via the Hyper-V Manager and was able to launch it from VS2013.
Closing down some applications (eg SQL Server) did the trick for me.
I'm trying to set up a cuda development environment under windows, and lurked many cuda-tagged posts, but few things are still unclear:
Can I debug cuda applications under windows without the need of a second video card, using nsight and VS2010 express?
Can I debug cuda applications under linux without the need of a second video card, AND without shut down the graphical interface?
Answered thousands of times, but perhaps something has changed, so I ask again just to be sure: Can I develop under windows without installing a cuda-enabled video card? There is some kind of emeulator? (Ocelot for windows is practically inexistent).
Thanks.
Can I debug cuda applications under windows without the need of a second video card, using nsight and VS2010 express?
You can apparently debug with a single video card, but nsight requires vs2010 professional (not express edition)
https://developer.nvidia.com/nsight-visual-studio-edition-requirements
Can I debug cuda applications under linux without the need of a second video card, AND without shut down the graphical interface?
I don't think so, from the eclipse nsight docs (http://docs.nvidia.com/cuda/nsight-eclipse-edition-getting-started-guide/index.html#linux-requirements):
"A GPU that is running X11 (on Linux) or Aqua (on Mac) cannot be used to debug a CUDA application and will be hidden from the application ran in the debugger. Such GPU can still be used for profiling GPU applications."
Answered thousands of times, but perhaps something has changed, so I ask again just to be sure: Can I develop under windows without installing a cuda-enabled video card? There is some kind of emeulator? (Ocelot for windows is practically inexistent).
no, if you want to use cuda, you'd be best off just getting a cheap cuda-enabled card (e.g. a GTX 650 is ~$100 and is the most recent (kepler) architecture)
Nvidia has released extended eclipse for CUDA 5. They have Nsight plugin for VS2010 also. In VS2010 we can stop program execution at breakpoint in kernel but how to achieve this functionality in eclipse on Linux? I don't see any nsight specific keys to stop execution. I tried changing perspective but it debugs as a normal C/C++ application. I'm using Tesla C2070, Intel Xeon 8 core machine with Linux.
I'm from Nsight Eclipse Edition team.
Our goal is specifically for the application to be debugged as a normal C/C++ application. This means that you can set breakpoints, use "run to line", etc. regardless of whether you debug host or device code.
Basically, the process is quite standard for Eclipse:
Create a project (you can also import existing executable)
Click debug button
Debugger will run and by default will break in the main function. Note that no device code posted on the device so you will only see the host thread.
Set a breakpoint in the device code and hit resume (note that Breakpoints view toolbar also allows you setting breakpoint on any CUDA kernel launch)
Debugger will break when device code reaches the breakpoint. You can inspect your application state using visual debugger UI.
Couple things, and not sure which solved the issue. Drivers updated to latest ones with RC5.0, but I chose to run VNC server instead of native X server. Then the CUDA card(s) are dedicated to my apps and debugging, and it works like a charm, and now accessible from everywhere.
Eugene,
I just installed Cuda 5, and I wasn't able to break in any kernel code. It was a clean install of centos 5.5, with a fresh download of cuda-5, and i am running on a asus g71x laptop which has a gtx260m installed.
I thought maybe you cant run display and dedbug on one device still, so i switched to non-nv x display, but still had same issue, cant stop in the kernel code.
Have you tried CUDA 5.0 RC1? It is available now. You can download and try it. And I have tried the Nsight in it, it works well for debugging.
Best regards!
The 304.43 NVIDIA Driver does not let users other than root debug their CUDA application.
That problem is not present in any past or future public releases. The CUDA documentation recommends using only drivers listed in the CUDA DevZone. The 304.43 driver is not one of them.
That may or may not be the issue you are hitting. But I thought it was worth mentioning.