New post

Find

Question
· Dec 17, 2024

UDP Adapter not working

#ObjectScript #Ensemble #InterSystems IRIS

Hello

I am trying to work with UDP Connection/Adapter and I get this error.

ERREUR #5002: Erreur Cache: <WRITE>zSend+5^EnsLib.UDP.Common.1

 Here is the method
 

Class TEMPLATE.BO.UDPSend Extends Ens.BusinessOperation
{

Parameter ADAPTER = "EnsLib.UDP.OutboundAdapter";

Property Adapter As EnsLib.UDP.OutboundAdapter;

Method SendData(pInput As Ens.Request, Output pOutput As Ens.Response) As %Status
{
    Try {
        Set status=$$$OK
        Set pOutput=##class(Ens.Response).%New()
        
        Set stream = ##class(%Stream.GlobalCharacter).%New()
        Do stream.Write("This is some text")
        $$$LOGINFO(stream.Read())
        Do stream.Rewind()

        Set status = ..Adapter.SendStream(stream)
    }
    Catch exception {
        Set status=exception.AsStatus()
    }    
    Return status
}

XData MessageMap
{
<MapItems>
<MapItem MessageType="Ens.Request">
<Method>SendData</Method>
</MapItem>
</MapItems>
}

}

I have tried with ##class(%Net.UDP).%New() and it is working.

Does anyone have an idea of why it is not working or some example of a functionnal method, please ?

Thanks in advance

Corentin

PS : For those who don't want explore the code to find the line where it generate an error : 

zSend(pDevice="",pBuffer) public { Set:'($data(pBuffer)#2) pBuffer=""
    Set tStatus = 1
    Try {
        Do pBuffer.Rewind()
        Use pDevice Do pBuffer.OutputToDevice()
        Use pDevice Write !
    }
    Catch eSend {
        Set tStatus = eSend.AsStatus()
    }
    Quit tStatus }
2 Comments
Discussion (2)1
Log in or sign up to continue
InterSystems Official
· Dec 17, 2024
Open Exchange

IPM 0.9.0 Released

#InterSystems Package Manager (IPM) #InterSystems IRIS #InterSystems IRIS for Health #InterSystems Official

We have released IPM 0.9.0. I previously remarked on some of the history and reasoning here; to summarize, this is a big release for two reasons: it represents a long-overdue reunification of our internal and community-driven work around IRIS-centric ObjectScript package management, and it has some backwards incompatibilities. There are several necessary backwards incompatibilities in our roadmap, and we've lumped them together; this will not be some new norm.

Under the hood, the class naming and package structure has completely changed. If you're making direct use of calls to (most likely) %ZPM.PackageManager, the equivalent class is now %IPM.Main. For community projects that are impacted by this name change, we've submitted a bunch of PRs to get things up to date, and some use of old %ZPM.* class names is migrated automatically on installation via ZPM to allow packages to work with both old and new versions of IPM.

If you update from IPM 0.7.x to 0.9.0, everything should "just work" as before - it's available instance-wide, with data migrated to new storage locations.

On a new/fresh installation, things are a little different; by default, the community registry is not enabled, and IPM is only available in the namespace in which it was installed. To get to equivalent behavior of 0.7.x on a new installation, you need to run the following commands to map IPM everywhere and use the default community registry, respectively:

zpm "enable -map -globally"
zpm "repo -reset-defaults"

There's a 0.9.1 patch coming *very* soon (today/tomorrow - soon enough that I'll just update this post) which will streamline this process to some extent; see https://github.com/intersystems/ipm/issues/662 for context/updates.

If you encounter any issues or questions, please file a GitHub issue; we'll be keeping an eye out on the Developer Community as well.

3 Comments
Discussion (3)3
Log in or sign up to continue
Announcement
· Dec 17, 2024

VS Code release November 2024 (version 1.96)

#Development Environment #George James Software #Release #Studio #VSCode #Other

Visual Studio Code releases new updates every month with new features and bug fixes, and the November 2024 release is now available. 

This release includes some useful features for teams implementing VS Code, to achieve consistency and compatibility across organizations. If need help migrating from InterSystems Studio to VS Code, or want to advance your knowledge of VS Code, take a look at the training courses George James Software offers > georgejames.com/vscode-training/

Version 1.96 now includes: 

The release also includes contributions from our very own @John Murray through pull requests that address open issues. 

Find out more about these features in the release notes here > https://code.visualstudio.com/updates/v1_96

For those with VS Code, your environment should auto-update. You can manually check for updates by running Help > Check for Updates on Linux and Windows or running Code > Check for Updates on macOS.

1 Comment
Discussion (1)2
Log in or sign up to continue
Article
· Dec 17, 2024 10m read

Optimizing Performance of Apache Web Server and Web Gateway

#Beginner #Deployment #Performance #System Administration #Web Gateway #InterSystems IRIS for Health

 

Optimizing Performance of Apache Web Server and Web Gateway

By Patrick Jamieson, M.D., Product Technical Manager, InterSystems IRIS for Health

When working with InterSystems IRIS or IRIS for Health, an external web server like Apache2 or NGINX is essential for managing HTTP workloads, especially for FHIR servers. Starting with version 2023.3, the private Apache server was removed from the installation kit (except for Community Editions and Health Connect). This article provides practical tips to test and optimize the performance of your Apache web server and InterSystems Web Gateway configuration.

📋 Why Performance Optimization Matters

Out-of-the-box configurations are rarely ideal for production workloads. Optimizing Apache and the Web Gateway can significantly reduce response times, improve throughput, and handle higher concurrency under load.

🛠️ Testing Performance Using Apache Bench

Apache Bench (ab) is a powerful benchmarking tool that can simulate high load, identify bottlenecks, and measure metrics like response time and concurrency.

Installing Apache Bench

On Linux, install it with:

sudo apt-get install apache2-utils

Running Tests

Start by using a simple load test:

ab -n 100 -c 10 https://yourserver/endpoint
  • -n: Number of requests (e.g., 100)
  • -c: Concurrent requests (e.g., 10)

Apache Bench (bench) will now make 100 requests with a maximum of 10 requests running concurrently.

Here are my results using the Apache2 server with a default IRIS for Health server and gateway configuration settings with a FHIR server deployed on AWS.

Server Software:       

Server Hostname:        fhir.testintersystems.com

Document Length:        2303 bytes

Concurrency Level:      10

Time taken for tests:   1.161 seconds

Complete requests:     100

Failed requests:            0

Total transferred:         264500 bytes

HTML transferred:       230300 bytes

Requests per second:    86.11 [#/sec] (mean)

Time per request:       116.126 [ms] (mean)

Time per request:       11.613 [ms] (mean, across all concurrent requests)

Transfer rate:                222.43 [Kbytes/sec] received

*Connection Times (ms)

                         min      mean[+/-sd]    median            max

Connect:          4          20        8.6       18                     57

Processing:     3          87        177.9    17                    705

Waiting:           3          85        178.1    14                    701

Total:                19        107      180.0    38                    762

 

*Connect: How long it takes ab to establish a TCP connection with the target server before writing the request to the connection (ctime)

Processing: How long the connection was open after being created (time - ctime)

Waiting: How long ab waits after sending the request before beginning to read a response from the connection (waittime)

Total: The time elapsed from the moment ab attempts to make the connection to the time the connection closes (time)

 

* https://www.datadoghq.com/blog/apachebench/

So far, these statistics look good, but when then I increased the load on the server.

ab -n 2000 -c 75 https://fhir.testintersystems.com/csp/healthshare/demo/fhir/r4/Patient/1

 

Now I saw:

Server Hostname:        fhir.testintersystems.com

Document Length:        2303 bytes

Concurrency Level:      75

Time taken for tests:   10.811 seconds

Complete requests:      2000

Failed requests:        12

(Connect: 0, Receive: 0, Length: 12, Exceptions: 0)

Non-2xx responses:      12

Total transferred:      5265484 bytes

HTML transferred:       4583092 bytes

Requests per second:    185.00 [#/sec] (mean)

Time per request:       405.401 [ms] (mean)

Time per request:       5.405 [ms] (mean, across all concurrent requests)

Transfer rate:          475.65 [Kbytes/sec] received

 

Connection Times (ms)

                         min      mean[+/-sd]                median            max

Connect:           5         118      63.9                 120                  310

Processing:       7          284     835.4               86                    5397

Waiting:           3          262      838.6               65                    5384

Total:                12        402      831.5               205                  5417

 

Percentage of the requests served within a certain time (ms)

  50%    205

  66%    226

  75%    276

  80%    296

  90%    379

  95%   2069

  98%   4195

  99%   4832

 100%   5417 (longest request)

 

Notice with many more requests per second, the time to process each request has increased significantly to over 400 ms. I saw that a few of the requests didn't even return a response -- a failed request.

The bottlenecks required I modify specific configuration settings in Apache2 to address these performance issues. The Apache2 server ships with a selection of Multi-Processing Modules (MPMs) which are responsible for binding to network ports on the machine, accepting requests, and dispatching children to handle the requests. For instance, I  could adjust the MaxClients or ServerLimit directive to improve the number of concurrent connections the server can handle. I could also tweak the KeepAliveTimeout or Timeout settings to optimize how long connections are kept open.
 

⚙️ Identifying and Addressing Bottlenecks

Here are key optimization steps:

1. Modify Apache2 MPM Configuration

Edit /etc/apache2/mods-enabled/mpm_worker.conf:

<IfModule mpm_worker_module>
    ServerLimit            200
    StartServers           25
    MaxRequestWorkers      5000
    MinSpareThreads        75
    MaxSpareThreads        250
    ThreadsPerChild        25
</IfModule>

2. Tune Web Gateway Settings

  • Max Server Connections: 8000
  • Server Response Timeout: 900
  • No Activity Timeout: 86401

Restart Apache after changes:

sudo service apache2 restart

🚀 Retesting Performance

Re-run ab with higher concurrency:

ab -n 2000 -c 75 https://yourserver/endpoint

Monitor improvements in:

  • Requests per second
  • Failed requests
  • Connection times

Repeating the earlier bench command:
ab -n 2000 -c 75 https://fhir.testintersystems.com/csp/healthshare/demo/fhir/r4/Patient/1

I now saw the following statistics

Server Hostname:        fhir.testintersystems.com

Concurrency Level:      75

Time taken for tests:   5.975 seconds

Complete requests:      2000

Failed requests:        0

Total transferred:      5290000 bytes

HTML transferred:       4606000 bytes

Requests per second:    334.75 [#/sec] (mean)

Time per request:       224.045 [ms] (mean)

Time per request:       2.987 [ms] (mean, across all concurrent requests)

Transfer rate:          864.67 [Kbytes/sec] received

 

Connection Times (ms)

                                     min                  mean[+/-sd]                median                        max

Connect:                      6                      136      24.6                 135                              286

Processing:                  7                      84        23.4                 82                                171

Waiting:                       3                      47        18.8                 45                                160

Total:                            13                    221      28.3                 219                              363

 

Percentage of the requests served within a certain time (ms)

  50%    219

  66%    223

  75%    227

  80%    229

  90%    257

  95%    281

  98%    296

  99%    312

 100%    363 (longest request)

Notice with the retest (after performance tuning) the total connection time has dropped by 50%, and 99% of our requests are being completed within 312 ms, compared to the previous 4.8 sec. Notice also we are no longer seeing any failed requests.

 

📊 Monitor System Performance

This short post mentioned a few factors that could limit overall HTTP performance. Memory, CPU, and disk utilization could also create performance limitations. To understand these performance bottlenecks, it may be necessary to monitor system performance over 30 minutes to several hours.

Use the IRIS system performance tool to identify server-side bottlenecks:

Do ^SystemPerformance

📝 Key Takeaways

  • Optimize Apache’s MPM settings for higher concurrency.
  • Fine-tune Web Gateway configurations to align with Apache limits.
  • Use Apache Bench iteratively to test and validate changes.

Performance optimization is an ongoing process—continuously monitor, test, and refine your configurations to meet growing demands.

For further details, refer to IRIS Web Gateway Documentation.

Happy optimizing! 🚀

Discussion (0)1
Log in or sign up to continue
Question
· Dec 17, 2024

Production pooled component index

#Business Process (BPL) #SQL #InterSystems IRIS for Health

I have a business service which is responsible for some batch operations with an SQL table. The process is generally slow but it is possible to scale the performance using multithreading and/or parallel processing and logical partitioning (postgres):

6 Comments
Discussion (6)2
Log in or sign up to continue