The title pretty tells it all. I was having issues recognizing the table, the query function was failing on a key exception. I was able to figure out what was happening when I ran the same search to create the same table as my testcase and when I tried to open the html table editor my system froze for about 5 minutes. I then went back to my automation and added a 100,000 ms waitfor create statement to wait for the table to load. Now everything works. However this is very slow. Is there something I can do to optimize this table match?
Thanks! So to correct the title, I measured one test case that took up to 55 seconds to load the table. With your advice I removed several match rules and that time went down to 29 seconds. That is a big improvement. Is there anything else we can do to optimize?
Posted: 4 years ago
Posted: 12 Jul 2018 14:21 EDT
Kumaran Kannan (KK407007)