Jump to content

Recommended Posts

Posted (edited)

My site runs highly distributed in 15+ locations around the world. (Primary in Germany, read replicas in X other locations)

This results in great performance for the dynamic HTML (80ms from US West coast to regional replica), however all my asyncspc.php request still go to Germany (463ms to Germany)

I understand Revive Adserver needs Primary/Primary for full replication to work.

I wonder if I can go for a setup which ONLY sends asyncspc.php to many global (read-only) replicas. Any other request which reads/writes (eg. lg.php would go to the primary)

Goal:

- Make asyncspc.php as fast as possible (any delay here results in ads being shown later)
- Ignore the speed of lg.php, when this requests take a bit longer is not really important

revive.png

Does you know if such a setup will work as expected; or will there be hidden "writes" which are triggered by asyncspc.php?

Edited by Tim Vereecke
typos
  • 2 weeks later...
Posted

Hey Tim, I guess you could play a bit with deliveryUrl  settings and achieve what you need

Let's say your main delivery domain is delivery.example.com and the regional replica answer to delivery-edge.example.com

Now, you could set up delivery-edge.example.com as deliveryUrl on the master and delivery.example.com as deliveryUrl on the replica machines.

The tags you generate from the UI will use delivery-edge.example.com and the ads served from regional replicas will have lg.php pointing to the main delivery.example.com.

  • 3 weeks later...
Posted

Thx for the reply @Matteo Beccati

At the CDN level I can have everything on the same domain, and based on paths I can forward to different origins. (which works)

 

My question is basically, is asyncspc.php doing any writes?

 

if no, primary/replica database replication would work.

If it does, in that case full replication (primary/primary) is needed.

 

Posted
10 hours ago, Tim Vereecke said:

My question is basically, is asyncspc.php doing any writes?

 

if no, primary/replica database replication would work.

If it does, in that case full replication (primary/primary) is needed.

 

I guess it depends on whether or not you have request logging enabled.

This also seems a good opportunity to do a shameless plug for our Redis logging plugin: https://www.adserverplugins.com/redis-logging-plugin-for-revive-adserver/ - you'd be collecting stats on the edge on Redis and ship them to the master before maintenance.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...