Suggestion algorithm: Too many logs and DB connections

Description

Hi guys,

Since we have upgraded Requirement Yogi, our collaborative editing and Requirement Yogi aren't friends anymore.
Our backlog is filled with this error:
Requirements of the form Risk- can't be suggested because they use too many formats (REQ-100, REQ-1, REQ-001, etc). Please add leading zeroes to requirement numbers, so you can get suggestions again. Thank you!
And I cannot turn on the collaborative editing.

The error is not really clear for us... We have requirement yogi items called Risk-001, Risk-002 ... but we cannot find them anymore.

Environment

None

Observations

None

Activity

Show:
Adrien Ragot (Old account)
August 3, 2017, 9:12 AM

Ok, thank you very much both for your participation. Performance is a difficult thing because no two instances are the same (number of pages, number of spaces, number of requirements on each page, performance of the CPU, etc). If you ever want to check what is Requirement Yogi's load onto Confluence, then the REST URL above (/reqs/1/requirements2) is a good place to monitor.

I'll close this bug. You can keep commenting here, but for clarity, feel free to reopen new ones on performance topics, if need be.

Thank you both very much!

Jeff Ward
August 2, 2017, 6:34 PM

Looks like this is fixed. I'll let you know if we see any more issues.

Adrien Ragot (Old account)
August 2, 2017, 7:34 AM

Great Mathilde, but your confirmation is about the logs and features, not about performance. I'll wait for Jeff before closing the issue, in case he can check whether the "83 connections" symptom still occurs.

Mathilde Escudie
August 1, 2017, 10:46 PM

Same here, I wasn't aware of the isolate spaces feature, I will definitely use it.
You are right, I was talking about having unique keys for your entire instance so that you cannot have the same key in two different spaces because it generated the error above. Since we change the keys to make them unique, we have no error anymore.
I am happy with the resolution of this issue if you want to close it.
Thank you for your support!

Adrien Ragot (Old account)
August 1, 2017, 3:10 PM

Ok, "Isolate spaces" solves the problem that it returns requirements from other spaces when trying to insert a link. It doesn't solve that you want unique keys for the whole instance. I'll track the latter as RY-170.

Resolved

Assignee

Unassigned

Reporter

Mathilde Escudie

Labels

None

Participants

None

Components

Fix versions

Priority