Support Board
Date/Time: Sun, 29 Dec 2024 14:09:58 +0000
Basic Examples of How You Use INDEX, MATCH / Spreadsheet Performance Improvements Now Available
View Count: 5712
| [2016-01-13 01:06:19] |
| |
|
We will be releasing version 1354 probably today. Questions related to 1354: 1. Does GetCorrespondingMatch in 1354 meet all of your requirements? Do you need the capability for multicolumn search? In other words searching a range that is more than one column. 2. We have not done any major optimizations to MATCH when searching an ordered Range. Is there any reason why you would need to rely on MATCH any longer? 3. Do all of the performance improvements as of version 1354 make using New Spreadsheets of acceptable performance? Also, in the problem highlighted here: https://www.sierrachart.com/Download.php?Folder=SupportBoard&download=6793 The problem is the SearchRangeOrderingFlag parameter is indicating that the column is ascending when it is unordered. So it needs to be 0. There are additional performance improvements we are working on, but these are going to take a little more time and the benefit of them is just going to depend upon the data and the Formulas in the spreadsheet. So they could make a significant difference, or negligible difference. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-01-13 02:50:31
|
| [2016-01-13 02:51:39] |
| |
|
The prior post has been updated. Another thing we noticed is that after pasting a formula into another cell, the result of that formula is incorrect. We think this is the reason for some similar issues we have seen reported with New Spreadsheets. This will be fixed tomorrow. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-01-16 20:04:00] |
| |
|
Letting you know version 1355 has been released and has all of the latest New Spreadsheets improvement/fixes.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-01-19 14:35:18] |
| Sawtooth - Posts: 4143 |
|
Sorry for the delay in responding. The following comments are based on v1355. Does GetCorrespondingMatch in 1354 meet all of your requirements?
1a. Not yet. See #2 below. (An optimized INDEX/MATCH would.)Do you need the capability for multicolumn search?
1b. I've never had the need, but maybe others might.Is there any reason why you would need to rely on MATCH any longer?
2. Yes-GETCORRESPONDINGMATCH is untested in all situations where I use INDEX/MATCH. -Attached scss is an example. MATCH is used in column Y to assign descending numbers to each row, then formulas in columns T-X return the offset row that INDEX uses in columns H & I to return the corresponding values at the implied value of 1. Do all of the performance improvements as of version 1354 make using New Spreadsheets of acceptable performance?
3. Not yet. Performance of INDEX/MATCH and GETCORRESPONDINGMATCH in the test spreadsheet are now acceptable, but only if I'm not connected to TransAct. When connected to the data feed, there is lag at every chart update.
|
 Zigzag previous legs.scss - Attached On 2016-01-19 14:25:27 UTC - Size: 105.28 KB - 442 views Zigzag previous legs.cht - Attached On 2016-01-19 14:34:10 UTC - Size: 48.09 KB - 465 views |
| [2016-01-19 17:57:30] |
| |
|
Thank you. We will see how best to solve all of this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-01-26 05:36:05] |
| |
|
Regarding post #28, update to the latest prerelease of Sierra Chart and perform your testing again.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-01-26 05:38:26] |
| |
|
We also want to report this users feedback about the performance improvements: Accurate Replay Duration Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-01-27 01:00:53] |
| Sawtooth - Posts: 4143 |
|
v1358 has significant performance improvements involving the New Spreadsheets, using my test spreadsheet studies. Performance is equal or better than the Old Spreadsheets. The increased performance might be even more noticeable in situations different than my test spreadsheet revealed, as noted by user @sigmadict. Performance is actually significantly much better than the Old Spreadsheets test spreadsheet, when connected to my data feed, and using INDEX/MATCH in both. However, the GETCORRESPONDINGMATCH function cannot be used in the Zigzag Previous Legs example in post 28, where INDEX and MATCH are not used in the same formula. But that's not a problem since INDEX and MATCH are now also optimized. These performance improvements have allowed the use of INDEX/MATCH combination without any lag in every situation I've tested up to this point. This is much appreciated. Thank you for the time and effort you've put into these performance improvements. |
| [2016-01-27 06:09:10] |
| |
|
This is good. Just let us know if you need any other functions added or notice any other performance issues.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: