Skip to content

Conversation

@david1437
Copy link
Contributor

No description provided.

@github-actions
Copy link

@david1437
Copy link
Contributor Author

CI errors seem unrelated

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for doing this. Here are some comments.

Also, can you rebase on git master?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be value_set_length.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the first call for warmup?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes exactly

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't seem logical to add this second term. The "items" processed are the input array items.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Call this "SmallSet" instead of "Small"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"LargeSet"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 << 20 sounds very large and irrealistic for a lookup set. How about 1 << 10 (which is already quite a lot of lookup strings).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, for more realistic data, how about using std::numeric_limits<Type::c_type>::max() instead?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may cut down on the number of benchmark instances and use RangeMultiplier(4) instead.

@david1437
Copy link
Contributor Author

Not too proficient with git so hopefully, I rebased correctly. Added changes as you recommended.

@pitrou
Copy link
Member

pitrou commented Nov 9, 2020

Ok, it seems the git situation is still a bit messed up, I'll fix it up :-)

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @david1437 . I'll merge if CI is green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants