Proctor Performance

[Arvind Kalyan]

Hi, 

Proctor is a really amazing framework. We are thinking of using it for our in house A/B Testing (tried out planout4j and sixpack as well. picked proctor! )

I have combined proctor-webapp and proctor-pipet to write and read JSONs to/from a common SVN repository. I have a cron which checks out a local copy of the changes in text matrix every 10 mins, which also runs proctor-maven-plugin to generate the new test matrix json file. The scheduledExecutorService will then pickup the new JSON every 60 seconds, which I configured in the pipet.reload.seconds in the properties file of pipet.  

I'm a little skeptical about the scalability though (need to do some testing ). Can you provide me some data regarding the performance of Proctor? Also do you have data on which all companies use Proctor?

Much appreciated. Kudos to the team that built it. 

Thanks, 
Arvind.

[ketan]

Hi, Arvind.  We don't know all the companies that use Proctor.  We do know of some use at About.com and HomeAway, and of course Indeed uses it heavily.  If you are not familiar with Indeed, we have over 180M unique visitors every month who execute many billions of searches in total.

Proctor executes on every page request, including for our highest traffic properties.  Our internal testing and real world experience indicate that Proctor adds no meaningful cost to request processing.  I'm not sure what scale you are running at, but I can't think of a case where a reasonably-configured and provisioned Proctor would ever be the bottleneck in a web application.