Vlookup Delay

Vlookup Delay - Messages

#1 Posted: 2/18/2018 12:15:39 PM
NDTM Amarasekera

NDTM Amarasekera

130 likes in 352 posts.

Group: User

An automatic electronic device had been installed on the bank of a stream to record and transmit Water Levels (at half hour intervals) to a control center, where the readings were converted to discharge values, for further analysis, using an already established Rating Table. These data are given in an Excel file.

The attached SS file takes nearly 2 minutes to convert 1 month data values (48x31=1488).
I have tried this with several previous SS versions also.
Can this be improved, as we have to deal with data recorded for over 5 years?
My system: Win 10 Pro, 64 bit, Core i5, 6 GB Ram Laptop.
Any help will be much appreciated please

WL To Q.sm (18 KiB) downloaded 42 time(s).
1.July WL&RT.xlsx (29 KiB) downloaded 61 time(s).

File not found. File not found.
Look within!... The secret is inside you. Best Regards Eng. NDTM Amarasekera - Sri Lanka
#2 Posted: 2/18/2018 3:42:00 PM
Andrey Ivashov

Andrey Ivashov

2270 likes in 3734 posts.

Group: Super Administrator

Hello.

First impression is that you should try using findrows(...) function (built in into the program) in this case.

findrows_1.PNG

vlookup(value,table,column):line(findrows(table,value,column-1),1,1)

Before change:
2 min. 14 sec.

After change:
2.4 sec.

But I see different results of using vlookup implemented in your worksheet (returns 1488 rows vector) and findrows (returns 2976 rows vector). Unfortunately I have no chance to deep into the logic, but this may be a good starting point.

Best regards.
#3 Posted: 2/18/2018 4:23:08 PM
Andrey Ivashov

Andrey Ivashov

2270 likes in 3734 posts.

Group: Super Administrator

Did find 5 minutes more to look into it and finally I did it:

WL To Q_mod1.sm (16 KiB) downloaded 62 time(s).
Takes 1.7 sec. on my environment.

Best regards.
#4 Posted: 2/18/2018 5:19:13 PM
Jean Giraud

Jean Giraud

983 likes in 6866 posts.

Group: User

Wrote

First impression is that you should try using findrows(...) function (built in into the program) in this case.



Maybe the other way around => vlookup needs be doctored.
Mine works fine 0.06 s scanning 9 rows for one value
FindRows => 2.4 s scanning 31 rows ... for ONE value, is it ?

Utilities Matrix lookup.sm (11 KiB) downloaded 58 time(s).

#5 Posted: 2/18/2018 11:16:33 PM
NDTM Amarasekera

NDTM Amarasekera

130 likes in 352 posts.

Group: User

Wrote

Did find 5 minutes more to look into it and finally I did it:

  • New Posts New Posts
  • No New Posts No New Posts