first of all thanks for making cameyo - a blessing!
unfortunately i've run into one problem i cannot solve, hope someone here can shed some light onto it....
we have one application for recording working hours of personnel i would like to virtualize;
it registers a whole bunch of .dlls and other libraries on the client (e.g. COMDLG32.OCX, msvcrt.dll, MSVBVM60.DLL and many more..)
i've successfully packaged it with cameyo (latest version) and basically it is working - however it's dead slow. e.g. the calculation/processing and saving of the entered working hours to the database file (not virtualized of course) takes up to 5 minutes or more, where on a non-virtualized installation of the program it takes mere seconds.
i've tried debugging my cameyo package in many different ways but it always comes down to the same conclusion: with cameyo: working but SLOW, without cameyo: FAST. of course i understand that there is a speed penalty involved due to the virtual layer cameyo adds, but surely not like this?i've already used cameyo to virtualize a small number of different apps, but never encountered such a huge impact on performance before.
anyone have some advise what i might have overlooked here or some information if this is a known problem with some applications or libraries in particular?
Are all necessary files deployed, or is possible that the slowness you're seeing is the result of Cameyo writing files it needs to disk? You can test this by using -ExtractAll parameter. If you still see the slowness after all files have been deployed from the package, then it's a different matter.
For testing purposes, is it possible for you to try writing to local database files? This would let us know if the problem has to do with writing across the network. Thanks.
thanks for the good idea - tested it right away and result is the same - very slow processing / loading and especially saving of the input data.
i even set the sandbox isolation mode to "full access", so that writing to disk should not be a problem at any point
in fact it is very small data that gets effectively written to disk since it's only records of working hours...
most of the slowness seems to be CPU related (the application's .exe consumes 100% cpu during the waiting time)
i've also tried putting the entire program installation in the package (including application and database files) just to see if it makes a difference, and it is dead slow as well...
i'm really lost here and about to give up on this one...
is there any way of extended debugging/logging during execution of a cameyo package, that might shed some light on whats taking so long?
Thank you for following up. Yes, the developer has the package, but no, hasn't had time yet to look into it. It is of interest, so I hope you can bear with us.
sorry for bumping a over 4 yrs old thread but I've kinda similar issues here.
Before re-installing my windows everything was fine but now It takes forever to save a Package. Creating a Package from installation is very fast but editing and saving It with an other name takes forever. CPU usage is at 100%~~
Does anyone know meanwhile how to solve this Problem? - thanks.
