| Panel |
|---|
This article applies to: Deskzilla 1.x-2.1 |
Problem
When there are many issues on the server, you may notice that Deskzilla can download and store more issues in the local database than it can efficiently handle. For example, when there are too many issues in the local database, Deskzilla can consume a lot of memory and CPU.
...
| Info |
|---|
This problem has been around for a while, and it will be fully solved in the future versions of the applications. |
| Anchor | ||||
|---|---|---|---|---|
|
Solution
To solve the problem described above, we recommend you to to either configure connections or download fewer issues, and if it still does not improve the application performance, you can clear your database.
| Anchor | ||||
|---|---|---|---|---|
|
Configuring Connections
You have configured one or more connections to work with the application. Please make sure they are optimally configured.
...
| Anchor | ||||
|---|---|---|---|---|
|
Downloading Fewer Issues
If there are more issues in a single project than Deskzilla can handle, you shouldn't download all of them in the local database. Create a query that describes the issues that you're working with (for example, "all open issues or all issues assigned to me"), and make it top-level query. Create sub-queries under that query to make sure you won't download unnecessary stuff.
...
| Anchor | ||||
|---|---|---|---|---|
|
Clearing Local Database
If you already have downloaded more issues than it feels comfortable, the only way to remove them from the local database is to completely clear it and download relevant issues once again. Please see How to Clear Local Database.
...