Reduce polling interval on Mesop and modify chroma dependency as it fails on windows

[jkfnc]

Can you please reduce polling interval to 100 seconds or something , the Mesop UI is freezing with continuous polling from demo/ui/components/page_scaffold.py

Also crewAI using chroma-hnswlib==0.7.6 fails on windows without Compiler and other libraries, would be best to use some other library instead.

[pstephengoogle]

Hi, thanks for the feedback. The polling is necessary to have dynamic UI (e.g. the responses show up automatically). We propose to add a UI element to disable polling or change its rate. If you disable polling, or use a very long delay between polls, you will have to manually sync (navigate to a new page and back) to see update events in the UI.

Currently investigating the chroma dependency and windows. Will update when we have a fix available

[rajeshvelicheti]

To get the chroma dependency, could you try this before you run the agent

uv python pin 3.12

This should unblock you, while I look further in to options.

[pstephengoogle]

Hi, we have put out #75 to address the polling optionality. Be warned, if you turn polling way down you will need to manually refresh to see any updates

[rajeshvelicheti]

And for chroma on windows it appears more involved than in mac / linux. I had to follow these steps to get it working

1. Download and install VC++ build tools https://visualstudio.microsoft.com/visual-cpp-build-tools/. Install all if okay, but at minimum the applicable build tools (Desktop development with c++) and base build tools.
2. uv venv
3. .venv/Scripts/activate.ps1
4. uv run .

[HeetVekariya]

@jkfnc

This issue is partially similar to #96 , so this is the temporary solution I find.

Okay, Let me summarize everything.

Problem :

• Demo UI is lagging so much, that users get experience of nothing happening in the background.
• Navigating between different pages takes way longer time.

Cause :

• Polling is happening with very low duration of the time difference, i.e. 1 sec.

---

• UI works perfectly on MacOS as multiple Mac users confirmed that.
• I tried demo/ui on two different systems, Windows i5 and Windows i7 and found this temp fix for windows.

Solution :

• Run the agent(s) before starting UI to avoid the connection error.
• Start UI.
• When the UI loads, i.e. you hit http://localhost:12000, first of all click to Disable button on the top right corner to disable the auto refresh and reduce the polling overhead. Wait until the polling stops, you can it in the terminal. (NOTE - If you navigate between pages using url, polling time will reset to default value which is 1 second, so navigate using the UI only.)
• Add agent(s) using agent tab.
• Jump to Conversation page and start new conversation.
• UI automatically refreshes whenever user sends a query, so when user asks something, UI gets updated and it gets reflected in the UI.
• To see further steps, you need to manually refresh the page using the refresh button present at the top right corner. You will something like below, until the response is available and at the end response when it is available.

---