Hi Guilherme.
I think your best starting point will be providing your system specifications, the OS you're running Studio on, and the version of Studio/Cache you are running.
Depending on the issue it could be anything that is causing your problems.
You could run the compile command you would use in Terminal within Studio using the output window. However, the only "speed boost" would be time saved from not launching and logging in to Terminal.
If you're suffering from really slow compile times, it might just be that your namespace is huge, or a sign of a need to upgrade your hardware.
Get in touch with either WRC or your sales engineer, and they'll happily help out.
Thanks for the response.
It sounds like I should be fine with the machine I'm running (Win7, 120GB SSD, 8GB RAM, i5 CPU (dual core)).
My biggest hits are at start up, but once up and running it's pretty snappy. I should probably try to be more patient!
That's it, that's what I was looking for.
Thanks!
The accepted answer would probably be your best shot.
Say for example you wanted a count of all messages that have come from a service called "TEST Inbound", you could use the SQL query option (System Explorer>SQL) to run the following:
If you wanted to put a date range in as well (which is advisable if what you're searching is a high throughput system and your retention is large):
Hi Gadi.
Glad to hear you have something in place now.
I guess a task is better for specifying the exact time for the event to run rather than every x number of seconds, as the timing could go out of sync if the service was restarted at any point.
For the setup I have, because I want to check the status of the drive free space (and I also check a specific folders files to alert if any of them have existed for more than 5 minutes) it makes sense to just let the Call interval run every x seconds.
I use a similar approach to Edwards answer (using a BS that runs every x seconds), but for alerting when freespace on my drives fall below a specified value.
I'm not sure if my approach is the most efficient to your requirement, but I would do something like this in the Service:
Thanks Joyce, I made contact with them instead of support, and after a webex the solution was found!
It turns out the performance issues I had been getting when adding the entire namespace was because I had included all of the system folders (ens, enslib, EnsPortal, etc). So on each launch, Eclipse was then reindexing the entirety of the core files in each namespace.
I tried this as a way of moving everything so far into our source control system, and the performance impact on Eclipse/Atelier was soul destroying.
Thank you Joyce, I will make contact with support.
Hi Izak.
What task would Ensemble be completing to link the two applications together?
Hi Bob. Please can you try running the task without KeepIntegrity selected?
If this doesn't resolve your problem, I'm all out of ideas.
Hi Bob. Do you have KeepIntegrity selected?
I ask because the only thing I can see which might point in the right direction is that the selection of message headers when KeepIntegrity is selected does a "select top 100000000" and your Ens.MessageBodyS is a digit greater (10 digits vs 9), so it could be that the items are somehow being missed? If this is the case, running the purge without the Keep integrity selected might work?
Also, I assume you are getting a success status from the task running?
Hi Bob.
These will be picked up by either Purge running the all command, or by selecting "Messages" for TypesToPurge in either one.
The MessageBodyS should be purged when the "BodiesToo" tick box is selected in the task. The description for the BodiesToo option is: "Delete message bodies whenever their message header is deleted. This is off by default because some Productions may use message objects that are part of a larger environment and not transitory." so it may be that your task was left with the defaults and this has built up.
Hi Bob.
I ran a comparison against the two Tasks to find the answer.
Basically they're almost identical, except that Ens.Util.Tasks.PurgeMessageBank includes the ability to purge "Message Bank Events" and "Message Bank Messages" using the "ALL" Parameter in TypesToPurge or by individually selecting them. So using Ens.Util.Tasks.Purge with all selected will not touch the Message Bank.
My guess would be that Intersystems either added Ens.Util.Tasks.PurgeMessageBank when the Message Bank functionality became available and didn't want to edit the Ens.Util.Tasks.Purge task so that ALL started to include purging the message bank, or Ens.Util.Tasks.Purge exists to be able to have a task which can purge all except the message bank so that customers that would like to purge all except the message bank can do so with one task rather than 7 separate tasks.
Hi Mark.
After throwing in an if statement for the Priority variation and some other local tweaks I have this working perfectly, so thank you for sharing.
I also added the Token and User Key as a setting to be set from the Operation within Ensemble.
It would be good to catch up outside of the Intersystems forums sometime soon.
Cheers!
For anyone interested in adding the Token and User Key
So I included before the method:
Property Token As %String;
Property User As %String;
Parameter SETTINGS = "Token, User";
And then the http request parameter became:
Do httprequest.SetParam("token",..Token)
Do httprequest.SetParam("user",..User)
This leaves the token and user key to be configured within Ensemble via the Management Portal:
Hi Mark, interesting stuff as usual.
Does your implementation go on to take advantage of the notification priorities? I'm just thinking of what benefits could be gained for alerting on-call staff to issues.
Hi Robert.
I think you have hit the nail on the head - the method return type is a string.
Time to do a bit of rework in the Dev environment...
Hi Jeff, thank you for your reply.
I did end up raising a call for this and, as I was unable to replicate the issue at the point of raising the call, it was decided that the call would be closed and a new one raised if it reoccurred.
Hi Lorraine.
I think the issue is that the Constraint is not set for the condition to be able to reference the filename. I see that you have added a comment to another post which explains how to do this, but it stops short in explaining fully. Fortunately, Joshua Goldman then links to another post where he goes in to more detail.
I'll copy and paste it here, and include the link.
https://community.intersystems.com/post/how-route-file-based-file-type
Docker sounds interesting, I'll give it a try next time.
Thank you - I will try this the next time I'm running a big job and see what details I get.
Thank you David, that was exactly what I needed.