Comments
Sort by recent activity
Please contact support@Red-gate.com, mentioning this forum discussion in your email. Our support team should be able to help you work this problem out. / comments
Please contact support@Red-gate.com, mentioning this forum discussion in your email. Our support team should be able to help you work this problem out.
Before the base service starts consuming large amounts of memory (e.g. <1GB), is behaviour normal? Do the problems with the website (5min delay, not loading, etc) only start to occur when the memory-use becomes excessive? / comments
Before the base service starts consuming large amounts of memory (e.g. <1GB), is behaviour normal? Do the problems with the website (5min delay, not loading, etc) only start to occur when the memor...
You say: "And we are unable open monitoring tool url and we are not geting alerts from it"
What happens when you go to you monitoring tool url? What error do you receive?
Try restarting the base service and the website. What happens then? / comments
You say: "And we are unable open monitoring tool url and we are not geting alerts from it"
What happens when you go to you monitoring tool url? What error do you receive?
Try restarting the base se...
Hi Joe. Thanks for the extra info.
As for the memory usage: this sometimes happens when SQL Monitor is doing something CPU intensive on a machine with lots of memory. When no other intensive processes are on the machine, the CLR sometimes grabs massives of memory for itself to amortize garbage-collections over very long periods, in order to free up the CPU. Generation 0 can become several gigabytes. This is just the CLR trying to be efficient by using all the resources available to it. Once the CPU is freer, it'll then hand the memory segments back to the OS.
As for the CPU: that is more worrying. What I believe is happening is that SQL Monitor was performing a large purge (i.e. deleting old monitoring data in your database). The purging algorithm is a bottleneck, since it has to sort and delete gigabytes of data. We'll investigate further. / comments
Hi Joe. Thanks for the extra info.
As for the memory usage: this sometimes happens when SQL Monitor is doing something CPU intensive on a machine with lots of memory. When no other intensive proces...
Hi Joe. To help with diagnosis, can I ask 2 questions:
1) How much memory is installed in each machine?
2) Are any other intensive applications running on each machine (e.g. a SQL Server), or is SQL Monitor the primary application?
Thanks! / comments
Hi Joe. To help with diagnosis, can I ask 2 questions:
1) How much memory is installed in each machine?
2) Are any other intensive applications running on each machine (e.g. a SQL Server), or is SQ...
You get this if the output path of the VS build is the same as the output path for SmartAssembly. i.e. You can get this error if "Output Path" in Visual Studio->Properties->Build is set to "\obj\Release\MyApplication.exe". It should be set to something like "\bin\Release\MyApplication.exe"
The PDB thing isn't about SmartAssembly's PDB option, it's about SA reading from the build output of VS (in obj\release) and writing it to the same file (in obj\release).
Tell me if this helps! / comments
You get this if the output path of the VS build is the same as the output path for SmartAssembly. i.e. You can get this error if "Output Path" in Visual Studio->Properties->Build is set to "\obj\R...
We've implemented this and it works. It'll be in the next release of SmartAssembly. / comments
We've implemented this and it works. It'll be in the next release of SmartAssembly.
I've tried to reproduce this, but the BAMLViewer loads and works fine for me. Exactly what error do you encounter? / comments
I've tried to reproduce this, but the BAMLViewer loads and works fine for me. Exactly what error do you encounter?
Nice idea. However, I suspect we wouldn't be able to do it. We would have to either parse the code and guess what things mean, which would be very fragile; or store metadata about every word in the decompiled code during decompilation (which I believe is what you were suggesting), which would be v expensive it terms of time and memory, and v hard.
I'll ask Alex Davies, the developer of this feature, about this issue. / comments
Nice idea. However, I suspect we wouldn't be able to do it. We would have to either parse the code and guess what things mean, which would be very fragile; or store metadata about every word in t...
Unfortunately the 'Go to decompiled definition' from decompiled code does not work. This is due to a technical limitation - decompiled code has the same status as a code file opened in Visual Studio which is not associated with a project (e.g. as if you opened a .cs file from explorer). Visual Studio doesn't even try to parse the code, hence we cannot identify the item we need to go to.
Sorry for this, we'll try to make this limitation more obvious in future versions. / comments
Unfortunately the 'Go to decompiled definition' from decompiled code does not work. This is due to a technical limitation - decompiled code has the same status as a code file opened in Visual Stud...