Pass offset and limit query parameters to MS Graph API about helix-data-embed HOT 3 OPEN

Testing shows that the new behaviour is actually slower because it consists of 2 more requests to the Graph API, which seems to outweigh the smaller responses being returned. On average, the new behaviour will cause data-embed to take 8s as opposed to 6s for the old behaviour.

A small optimization where only the values of a range are returned (not all the other information listed above), shows a slight performance gain in the range of 1-2 seconds.

from helix-data-embed.

Testing shows that the new behaviour is actually slower because it consists of 2 more requests to the Graph API, which seems to outweigh the smaller responses being returned.

• why are there 2 requests more ? isn't it only one more for the column names?
• can you use $skip and $top instead of the address?
• when a table is used, the header names can be retrieved.

from helix-data-embed.

why are there 2 requests more ? isn't it only one more for the column names?

1 request for the used range address, 1 request for the column names, 1 request for the values (which are not adjacent to the column names when offset is not zero), as opposed to 1 request for all values in the used range, which include the header row.

can you use $skip and $top instead of the address?

already tried, has no effect, unfortunately.

when a table is used, the header names can be retrieved.

right, but this would still use one more request

from helix-data-embed.