Right now Dave Jones of 
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
We have done some testing on the Mirrornet but we really do have to test some aspects of the new writer on the live Hive chain and when we do that these tests show up on my dashboard:
That looks like a bad game of Missile Command from the early '80s when it should look more like this:
Each of the coloured circles represents a minute's worth of Podpings from each of the accounts which are listed on the right of the graph. Their vertical position on the right hand scale shows the number of IRIs (which are URLs of podcasts) sent by each account in a given minute. That value is typically below 10 but for the three main accounts, podping.aaa, podping.bbb and podping.ccc, it can be 40 to 100 IRIs in a minute: that's normal load.
You can learn about the dashboard and play with it yourself from this post.
Reasons and Mediums
The biggest new feature of Podping Hivewriter 2.0 is its ability to handle "Medium" and "Reason" codes.
Mediums
Up to now almost every podping sent has been either a podcast or a video. Everything sent by Dave's Podping.cloud service was a podcast and everything I send for 
video.
Going forward there will be new mediums such as music, film and audiobook (schema is on Github).
Reasons
This is where the new magic comes from. Whenever a podcast or video podcast updates we just use the reason code update. The most important new Reason codes relates to signaling that a livestream has started. We are adding live and liveEnd to the existing update. (schema on Github).
This is where the magic happens and has already been in use for signaling the live streams from the No Agenda Podcast and other shows which then show up in Podverse and Curiocaster. There are other apps working on surfacing these live streams.
Rates
So why the missile command look on my dashboard? We are stress testing. Now that we're using multiple reasons and mediums in our podpings, we have also moved to writing multiple different Podpings (each a custom_json) into a single Hive transaction. That looks like this on the Hive chain.
And this is to ensure that we can comfortably handle more than the entire world's podcasts.
Right now Podcastindex.org records that 360,000 new podcast episodes were published in the last 30 days.
Podping broadcast 823,622 individual RSS feeds in the last 30 days. Whilst Podping appears to carry a higher number, not every time an RSS feed gets Podping'ed is it to announce a new episode. Many of those pings will be updates to show notes or other details.
We don't know exactly what proportion of new episodes are announce with Podping, the best guess is around 15%. But we want to make sure that when it rises to be all of them, we can cope.
Testing indicates we have plenty of overhead.
Podping's transaction volumes
https://twitter.com/v4vapp/status/1596902340019519488
- v4vapp
https://twitter.com/v4vapp/status/1596907162617397251?s=20&t=R7I2umvRXmD4-wECyPfW5w
- v4vapp
Thank you for looking all the way down to here, if you value my work on Podping, and on 
Support Proposal 244 on PeakD
Support Proposal 244 with Hivesigner
Support Proposal 244 on Ecency
