Normally, I wouldn't use that kind of percentage, except I wanted to highlight the large gap between the two protocols with Auth is used. JSON-RPC calls stay around 56 ms regardless of what I enable or disable in db.py. But for some reason, XML-RPC falls from 45 ms to 18 ms when Auth is disabled. Also keep in mind that the server is not running on the same machine as the test client, so for it to only take web2py 18 ms to respond to XML-RPC requests over the network (when not using Auth), that is awesome, but scares me at the same time.
- [web2py] Re: RPC Performance Testing with Sessions and SS... Ross Peoples
- Re: [web2py] RPC Performance Testing with Sessions and SS... Jonathan Lundell
- Re: [web2py] RPC Performance Testing with Sessions a... Ross Peoples
- Re: [web2py] RPC Performance Testing with Sessio... Jonathan Lundell
- Re: [web2py] RPC Performance Testing with Se... Ross Peoples
- Re: [web2py] RPC Performance Testing wit... Jonathan Lundell
- Re: [web2py] RPC Performance Testing wit... Ross Peoples
- Re: [web2py] RPC Performance Testin... Jonathan Lundell
- Re: [web2py] RPC Performance Te... Ross Peoples
- Re: [web2py] RPC Performance Te... Jonathan Lundell
- Re: [web2py] RPC Performance Testing wit... Anthony
- Re: [web2py] RPC Performance Testin... Jonathan Lundell
- Re: [web2py] RPC Performance Te... Anthony
- Re: [web2py] RPC Performance Te... Jonathan Lundell
- Re: [web2py] RPC Performance Te... Jonathan Lundell
- Re: [web2py] RPC Performance Te... Ross Peoples
- Re: [web2py] RPC Performance Te... Jonathan Lundell
- Re: [web2py] RPC Performance Te... Ross Peoples
- Re: [web2py] RPC Performance Te... Jonathan Lundell