Skip to main content
T
trump6-Contributor
6-Contributor
October 20, 2025
Question

The library task list is slow.

  • October 20, 2025
  • 2 replies
  • 471 views

Version: Windchill Below 11.0

 

Use Case: I've added a filter condition for creation time (time range), and the library task list has become very slow. windchill version windchill10 M030


Description:

I've added a filter condition for creation time (time range), and the library task list has become very slow.

 

windchill version windchill10 M030

BT_13040796_0-1760943331412.png

 

BT_13040796_1-1760943509683.png

 

 

2 replies

Fadel
Fadel23-Emerald I
23-Emerald I
October 20, 2025

Can you add the screenshot's in English 

Buiꓘa
T
trump6-ContributorAuthor
6-Contributor
October 21, 2025

BT_13040796_1-1761009635566.pngBT_13040796_2-1761009688342.png

BT_13040796_3-1761009722110.png

Querying all data is faster than adding a creation time range query. The creation time filter logic is not pushed down to the database; instead, filtering is performed via memory and CPU, and there is no full table scan in this case.

Additionally, my computer resources are very sufficient.
I suggest you decompile the following code to check the logic: the creation time isn't pushed down to the database, and the filtering is done in memory. Please help with in-depth research.
joe_morton
18-Opal
joe_morton18-Opal
18-Opal
October 20, 2025

If it fits your use case, add more filtering criteria. I see in the screenshot that over 2000 items was returned. If you can filter to return less data, the performance will be better.

 

Alternatively, try removing some columns if there are columns you don't need in the view. This will also improve performance.

 

Lastly, consider if your Windchill server has enough resources. 

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
October 20, 2025

I would also suggestion watching the database transactions when the page is selected, on a quiet time. Look for long running queries. You might be able to identify the query or it doing a full table scan. An index can be created to speed things up or perhaps looking at existing indexes, reformulate the filter to achieve similar results to take advantage of existing queries. Also consider upgrading to supported version.

T
trump6-ContributorAuthor
6-Contributor
October 21, 2025

Querying all data is faster than adding a creation time range query. The creation time filter logic is not pushed down to the database; instead, filtering is performed via memory and CPU, and there is no full table scan in this case.

Additionally, my computer resources are very sufficient.BT_13040796_0-1761009343122.png

 

Terms & ConditionsCookie settingsAccessibility statement