Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
8 replies
Subscribers
10 subscribers
Views
4169 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
I have indexed all database columns of the three tables feeding the database vie
mohamedb
over 8 years ago
I have indexed all database columns of the three tables feeding the database view this entity backed record grid is reading from. Still, the performance statistics show slow execution for the a!queryentity. I am attaching the numbers. Is this the norm Appian folks?
OriginalPostID-213822
OriginalPostID-213822
Discussion posts and replies are publicly visible
0
Jacob Cohen - Project Leader - Macedon Technologies
over 8 years ago
Have you querying the view directly from the database? What are the return times there? It's likely that the database is the hangup, not Appian.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Stefan Helzle
A Score Level 3
over 8 years ago
What do you mean with "indexed all columns"? Did you tell the database to create an index for each of the columns? This does not feel right. For a view it would be better to just index the fields you use for joining. Try to analyse your query. See
dev.mysql.com/.../using-explain.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jonathan Katora
Appian Employee
over 8 years ago
Those values seem really slow for a 20 row RDBMS query. From your expression, it looks like your constant is pointing to a view... is that correct? If so, you can look at the database performance logs to determine if your holdup is on the Appian side or RDBMS. See the performance troubleshooting section of this page:
forum.appian.com/.../Database_Performance_Best_Practices.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ChristineH
Certified Lead Developer
over 8 years ago
In addition to the log that Jonathan mentioned, execute explain plan on your view. How many full table scans are occurring?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Stewart Burchell
Appian Employee
over 8 years ago
...and as a long shot, if looking at the DB doesn't reveal any apparent issues it might be worth looking at the network latency using the browser tools (F12/Network)...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mohamedb
over 8 years ago
Had a look at Oracle's explain plan, looks like a database issue. Thank you guys for all the good ideas!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mpontius
over 8 years ago
Are you by chance either using an OR on the select that powers the view or potentially using an OR within Appian?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mohamedb
over 8 years ago
After doing a performance measurement both in Appian and in DB, I think it is a database latency issue. I use AND on the select that powers the view. Do you think there is an optimization around it?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel