Emmanuel
That is a big question and it depends on what you are doing.
If you are writing SQL queries, then look at the SQL performance statistics in INFORMATION_SCHEMA.STATEMENT_DAILY_STATS. 
If you are using an interoperability production, look at the activity and volume statistics.
For general database activity, you could use ^SystemPerformance as described, but with that you have to process the data with an extra tool and it is difficult to interpret. I suggest you enable the History Monitor. It will give you almost everything ^SystemPerformance gives you, with a fraction of the effort. You just look at the DB and CPU stats with SQL.

this applies to Ens.MessageHeader as well. The code is mapped to EnsLib which is normally mounted read only.
I think Tunetable is trying to update the class definition.
I can't remember if it has always behaved like this
 

you would need to give a lot more detail about  CustomEDI.SQLSIUInRequest and its ImportFromString method for anyone to tell you what is going wrong. What data type does the ImportFromString return, and have you tested it in isolation?

I think the 'normal' way to do this, would be to leave the HL7 message as an object. You could use a business process that extracts only the fields that are needed to retrieve the patient ID and send that to the SQL database. But i suspect you already have external logic that processes a whole serialized HL7 message.

https://community.intersystems.com/post/apm-finding-expensive-parts-you…

also describes how to locate expensive points in your code.

In this case you are talking about tiny differences. If this is executed millions of times in  a common path  that is executed frequently you might want to  think about it, but  for most applications it is not an issue. Those SQL queries that don't use an index are the killers.

The meaning is documented 

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

including information about when the alerts are sent and how often the sensors are sampled.

Changing he values is documented:

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

you have to navigate the options in 

do ^%SYSMONMGR

to edit the sensors. You have to then provide CPUusage (case sensitive) as the sensor you want to edit.

How many requests are you hoping to process? 10 per second? 100 per second? 1,000 per second? More?

The full answer to this question depends on how far you are trying to push the system.

If you have a general query this is a great place to ask.

But if you have an operational problem you should pick up the phone (or your preferred technology)  and call InterSystems support. The people there enjoy answering questions and getting systems back in action.

617-621-0700 in the US but if you google InterSystems Support i think you will get what you need worldwide.

John

the only place i can think of it being used in the pull down menu for selecting a target in a send. It only offers you configuration items that exist in the production you choose. If you haven't specified a production it lists everything it can find and gives you a big red warning.

There is nothing to stop you typing in a target that isn't on the list

dave

Before answering the specific questions, i will explain what business rules are for. (Routing rules are another story). Rules were invented to allow people who were not programmers to change code dynamically on a running system. That put a lot of constraints around them. It is the responsibility of the developer of the BP that invokes a rule to make sure the analyst who dynamically changes the rules can't do any damage, no matter how stupid or how malevolent they are.

If you are a programmer and your code is going through normal dev/test/promote cycles then you should probably just write a method of a utility class to do the work.  You can't do anything in a rule that isn't easier to do in code if you are a programmer. I will repeat that routing rules are another story.

to answer your points

1. You would have to post your code for a real answer but a few guesses.

  a) you can put values into context properties with an assign  elements

  b) the value that you <return> goes in the Result Location specified in the rule activity of the BP. 

  c) make sure you <return> when you have finished and don't continue through following <when> elements.

2. yes. you just use mulitple <assign> elments

3. a) lookup tables are designed for the case where you want to translate a lot of values. For example if you have thousands of product codes and their descriptions, that might be fixed of maintained on a regular basis, then lookup tables are the way to go.

3 b) Data transformations are for when you have two structures that are similar but not quite the same. For example an invoice might be represented slightly differently in two applications  but they are close and you want to move fields around between the two formats. A second example would be to change the values in a data structure, perhaps by using lookup tables to translate from the codes used by the sending application to the codes used by the receiving application.

It is hard to say, but i think the error is 'Invalid Name' and the reference to locks is just in the text of the long line of code where the error occurs. 

the name it says is invalid appears in the text but it doesn't look like valid COS to me so i can't see how it would compile. i would look at the cached query %sqlcq.DHCdAPP.892.INT and see what code it contains.

In the video i inadvertently said that the CSP Page statistics were not accessible through SQL. That is not correct. They are accessible through SQL by querying the table %CSP_Util.Performance.

My apologies for the mistake.

go to system configuration -> memory and start up and there is pull down menu at the bottom of the page to set the system mode.

It isn't as large as some people would like, but it shows red or green for live and dev.

if you find the local documentation hard to search for this kind of simple question don't forget the documentation is on line and google accessible. Entering 

site:docs.intersystems.com version

into google so you only search the intersystems documentation gives you a good set of hits.

For the second question - if you are on a test/development system and you are happy to remove all information about the status and queued messages you can use:

do ##class(Ens.Director).CleanProduction()

but it will destroy information so it must never be used on a real system.

I think the class name and the production name need to match so in Studio you use Tools->CopyClass to get a class with the meaningful name. And then edit the Production Name in the XData.

Class MyPackage.MyMeaningfulName Extends Ens.Production
{

XData ProductionDefinition
{
<Production Name="MyPackage.MyMeaningfulName" LogGeneralTraceEvents="false">
  <Description></Description>

look at http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

that might help.