Skip to content

Home

Development

IDEs

API Explorer

Releases

Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Optimizing web service performance

Logging payloads, monetizing, and throttling service invocations all at the same time greatly impacts Martini's performance. This is because as requests are received and responses are sent by Martini, data is also being processed and saved by Tracker and the invoke monitor. For every transaction, Martini must create multiple entries in a database and asynchronously add new documents to both search indices, all whilst using a broker to channel these events back and forth to ensure the distribution and execution of these events.

The throughput impact of Tracker and Monitor on web services is evident in TORO's test on web service performance. In this test, TORO compared Martini's REST web service throughput when Tracker and Monitor are both on versus when only Tracker is on. The results went as expected; turning off Tracker resulted in a major throughput boost by ~91.89%.

Can the invoke monitor be turned off?

If you're using Martini Online, invoke monitor logging cannot be turned off.

Turning off Tracker, whilst may improve performance, however, forfeits the ability to audit and troubleshoot transactions, resubmit failed requests, and create reports from Tracker data. With everything said, TORO recommends turning off Tracker if you don't plan on using any of its features.