Fire and forget issue

[oscarld]

I am trying to set increment in a sorted list using CommandFlags.FireAndForget, when i run 10000 sets not all them are setted in redis.

I am using this code:

for (int i = 0; i < 10000; i++)
{
	for (int i = 0; i < 24; i++)
	{
		string keyName = $"LR_moreviewed_{(i == 0 ? 23 : i - 1)}";
		db.SortedSetIncrement(keyName, value, 1, CommandFlags.FireAndForget);
	}
}

In the image, redis response.

Thanks for the help.

[oscarld]

This is a more accurated version of the code.

Random r = new Random();
for (int i = 0; i < 10000; i++)
{
	value = r.Next(1, 10);
	for (int i = 0; i < 24; i++)
	{
		string keyName = $"moreviewed_{(i == 0 ? 23 : i - 1)}";
		db.SortedSetIncrement(keyName, value, 1, CommandFlags.FireAndForget);
	}
}

[mgravell]

I notice you're incrementing 24 times per key - is this just a stress test? Or is this because you want to increment by 24? If the latter, you can specify the increment count in the parameter.

…

On 21 Apr 2017 5:23 p.m., "oscarld" ***@***.***> wrote: This is a more accurated version of the code. Random r = new Random();for (int i = 0; i < 10000; i++) { value = r.Next(1, 10); for (int i = 0; i < 24; i++) { string keyName = $"moreviewed_{(i == 0 ? 23 : i - 1)}"; db.SortedSetIncrement(keyName, value, 1, CommandFlags.FireAndForget); } } — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#616 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABDsK2WKX7tbgxzS1b7TN-Y7rs4H09Bks5ryNgOgaJpZM4NEgUW> .

[oscarld]

Marc, Thanks for the response,

No, I want to create 24 keys than will be expired periodically. The goal is to create a Most-viewed feature. I can share you the source code if you want.

[NickCraver]

Since these are fire and forget, are you letting the process finish sending before both exiting and checking the result? This would create a bit of a queue that may take a bit to drain depending on the horsepower involved.

[NickCraver]

Not enough info to go on here - closing out to cleanup.

[oscarld]

@NickCraver

Quite so!, I was running a console application that exit when the principal thread is finished.

Thanks and sorry for the delay.