rasa icon indicating copy to clipboard operation
rasa copied to clipboard

Possible memory leak

Open saswat0 opened this issue 1 year ago • 3 comments

Rasa Open Source version

2.8.26

Rasa SDK version

No response

Python version

3.6

What operating system are you using?

Linux

What happened?

I've deployed the demo chatbot at a certain endpoint and am using locust to stress test it. I have a single user (with 1 hatch rate) and am sending the message "hello" to the above endpoint to benchmark the application. Each time the server receives a request, the NLP engine tries to classify the intent and then responds back with an appropriate reply.

Here's my locust script:

class LoadCreate(HttpUser):
    wait_time = between(0.5, 0.51)

    @task
    def sayHello(self):
        payload = {"sender": self.name, "message": "Hello!"}
        response = self.client.post(apiUrl, json=payload)
        print(response.text)

The results from locust are quite abnormal to my understanding. Even when the number of users is constant (1), the response time keeps on increasing. Is there any explanation for this behaviour? I'm attaching the obtained plots herewith.

image

Command / Request

rasa run --enable-api

Relevant log output

No response

saswat0 avatar Jul 11 '22 08:07 saswat0

I tried hitting the NLU server (/model/parse) to find the root of this behaviour. Seems like rasa core is responsible for it Below plot shows two runs. First one (on the left) is the response time when only NLU is at play. Run 2 (right) shows the response time when both NLU and core are running.

total_requests_per_second_1657688198

saswat0 avatar Jul 13 '22 05:07 saswat0

hey @saswat0 , I'd be interested in trying to reproducing this - which bot did you use exactly when referencing the "demo bot"? Is there anything you changed config wise?

losterloh avatar Aug 03 '22 15:08 losterloh

No, I didn't make any modifications to any of the scripts. I installed rasa via and ran rasa run --enable-api

saswat0 avatar Aug 03 '22 17:08 saswat0

➤ Maxime Verger commented:

:bulb: Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS.

From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue!

:arrow_right: More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569.

sync-by-unito[bot] avatar Dec 16 '22 10:12 sync-by-unito[bot]