Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Production algorithm tricks anyone?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: Production algorithm tricks anyone?

#11

Post by kartiksura »

packersfan0000 wrote: post #10
kartiksura wrote: post #5

Earlier quoted context omitted.

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

Not to be a hater, but that seems like by far the most obvious way to do that, right?

Yes. It is intuitive to some. But I never learnt it from a text book. Thats why I was curious about such other tricks.

Re: Production algorithm tricks anyone?

#12

Post by borplk »

kartiksura wrote: post #5
bogomipz wrote: post #4

>"we had used a random number generator within a segmented number range." Could you describe your current implementation and its elegance?

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

Yeah not to be an ass but that's pretty standard. And cool too I admit.

Re: Production algorithm tricks anyone?

#13

Post by bogomipz »

kartiksura wrote: post #5
bogomipz wrote: post #4

>"we had used a random number generator within a segmented number range." Could you describe your current implementation and its elegance?

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

>"40% of the traffic Remaining has to be given to RTB"

What is RTB?

Re: Production algorithm tricks anyone?

#14

Post by bogomipz »

borplk wrote: post #12
kartiksura wrote: post #5

Earlier quoted context omitted.

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

Yeah not to be an ass but that's pretty standard. And cool too I admit.

>"Yeah not to be an ass but that's pretty standard."

Pretty standard in what context? Can you elaborate? Is there a name for the algorithm?

Re: Production algorithm tricks anyone?

#15

Post by kartiksura »

bogomipz wrote: post #13
kartiksura wrote: post #5

Earlier quoted context omitted.

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

>"40% of the traffic Remaining has to be given to RTB" What is RTB?

Real time bidding. It is used to trade ads with exchanges. When you dont have your own ads from your sales team.

Re: Production algorithm tricks anyone?

#16

Post by kartiksura »

borplk wrote: post #12
kartiksura wrote: post #5

Earlier quoted context omitted.

Ad 1 has to be shown 30% of the traffic Ad 2 has to be shown 40% of the traffic Remaining has to be given to RTB generate a random number between 0:100 if the number is 0-30 the Ad 1 has to be shown if the number is 30-70 the Ad 1 has to be shown else RTB is to be called The servers can be now independent and no need to share the state, or have a lock based counter. For large number of requests, and with a good rando…

Yeah not to be an ass but that's pretty standard. And cool too I admit.

It might seem standard among some circles. And i have learnt them on the floor. But could never find a book or blog which describes some more examples. I was curious if others had any ideas to share.

Re: Production algorithm tricks anyone?

#17

Post by anon263626 »

There's a bunch in Hacker's Delight.

One that comes to mind is XOR-swap. It's cute, but it's likely slower than using a temp var.

Some of the integer population count algos (1's counting) are clever.

Also, original Doom source has some neat tricks.

Re: Production algorithm tricks anyone?

#18

Post by kartiksura »

anon263626 wrote: post #17

There's a bunch in Hacker's Delight. One that comes to mind is XOR-swap. It's cute, but it's likely slower than using a temp var. Some of the integer population count algos (1's counting) are clever. Also, original Doom source has some neat tricks.

Aah finally a good clue about reading material. Thanks a ton.

Re: Production algorithm tricks anyone?

#20

Post by bogomipz »

kartiksura wrote: post #15
bogomipz wrote: post #13

Earlier quoted context omitted.

>"40% of the traffic Remaining has to be given to RTB" What is RTB?

Real time bidding. It is used to trade ads with exchanges. When you dont have your own ads from your sales team.

Ah OK thanks, for somer reason I was thinking the TB in RTB was token bucket and I was scratching my head at the first letter. Now I feel silly. Cheers.
Post reply on HN