Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-3230

Performance degradation in quarkus log manager

XMLWordPrintable

    • Hide 
      #Run the application

```
java -jar target/quarkus-app/quarkus-run.jar
```

## run JMeter
Open the file `slow-logs-jmeter.jmx` in JMeter. Then run the jmeter Test Plan. With 300 Threads (Users) Observer that the response time is ~1 second.

## collect a stack trace
In a separate terminal, use `jps` to get the process id of the running java application

Observe that all threads are BLOCKED on a semaphore in the logmanager:
```
jstack <pid> | grep -A5 BLOCKED
```
      Show
      #Run the application ``` java -jar target/quarkus-app/quarkus-run.jar ``` ## run JMeter Open the file `slow-logs-jmeter.jmx` in JMeter. Then run the jmeter Test Plan. With 300 Threads (Users) Observer that the response time is ~1 second. ## collect a stack trace In a separate terminal, use `jps` to get the process id of the running java application Observe that all threads are BLOCKED on a semaphore in the logmanager: ``` jstack <pid> | grep -A5 BLOCKED ```
    • ---

      Troubleshooting performance issues where the response time of our Quarkus application goes from 100ms to over 10 seconds under load (over 300 users accessing it).

      Reproducer attached

        1. slow-logs.tgz
          240 kB
        2. jstack.txt
          489 kB

            gandrian Georgios Andrianakis
            rhn-support-kkakarla kodandaRamu kakarla
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: