Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Composer nearly unusably slow for editing dialogs after updating to 1.3.0 #5396

Closed
3 of 8 tasks
ttur opened this issue Dec 21, 2020 · 3 comments
Closed
3 of 8 tasks
Assignees
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. Team: Platform Type: Bug Something isn't working
Milestone

Comments

@ttur
Copy link

ttur commented Dec 21, 2020

Describe the bug

After updating the composer from 1.1.1 to 1.3.0 editing a complicated bot is so slow that actions (such as editing a sendresponse) take 5-10 seconds, and occasionally fail.

Simpler dialogs can be edited okay, more complicated ones not at all.

We have been building an advisory bot since composer early betas. Our bot has 30+ dialogs. Simple dialogs have a few activities. Complex dialogs have a few hundred. We support three languages.

Most recently we were using version 1.1.1 and that worked quite well for this.

Version

Release: 1.3.0

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

Screenshots

Here is an example of the edit operation failing (editing Finnish version of the dialog that hasn't yet been properly translated from English):

image

Additional context

The process is taking just under 1G of memory on my laptop. I would be happy to give it more, if that helps, if I knew how.

It does not seem to matter whether the local bot is running or not. Editing is very slow and occasionally fails regardless.

@ttur ttur added Needs-triage A new issue that require triage Type: Bug Something isn't working labels Dec 21, 2020
@jwiley84 jwiley84 added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. labels Dec 21, 2020
@ttur
Copy link
Author

ttur commented Dec 22, 2020

Some testing results:

  • Release 1.2.1 is a bit faster than 1.3.0, but still way slower than 1.1.1 (tested on Windows and MacOS, same bot)
  • Removing our extra languages (Finnish and Swedish) – leaving only English – does not make 1.3.0 much faster; maybe a little

@gabog gabog added this to the R12 milestone Jan 4, 2021
@gabog gabog added Team: Platform and removed Needs-triage A new issue that require triage labels Jan 4, 2021
@gabog
Copy link
Contributor

gabog commented Jan 4, 2021

Thank you @ttur, we will address this issue in an upcoming release.

@cwhitten
Copy link
Member

This will be addressed in an upcoming patch (1.3.1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. Team: Platform Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants