On Thu, Apr 02, 2015 at 02:39:22PM -0700, Andy Zhou wrote:
> On Wed, Apr 1, 2015 at 4:17 PM, Ben Pfaff wrote:
> > On Thu, Mar 19, 2015 at 12:08:16AM -0700, Andy Zhou wrote:
> >> This patch set implements two ideas improve ovsdb connection scaling:
> >>
> >> * Allow multiple jsonrpc connection to s
On Wed, Apr 1, 2015 at 4:17 PM, Ben Pfaff wrote:
> On Thu, Mar 19, 2015 at 12:08:16AM -0700, Andy Zhou wrote:
>> This patch set implements two ideas improve ovsdb connection scaling:
>>
>> * Allow multiple jsonrpc connection to share a single ovsdb monitor, thus
>> maintaining a single set of ch
On Thu, Mar 19, 2015 at 12:08:16AM -0700, Andy Zhou wrote:
> This patch set implements two ideas improve ovsdb connection scaling:
>
> * Allow multiple jsonrpc connection to share a single ovsdb monitor, thus
> maintaining a single set of changes.
>
> * With in the same monitor, cache the json
On Sat, Mar 21, 2015 at 12:14:28AM -0700, Andy Zhou wrote:
> Here are the results:
>
> Without this patch series:
> ==
> #monitors delay of 20 transactions
> 1 0.046s
> 100 0.532s
> 200 1.007s
> 300 1
> I don't yet have any useful data on speed improvements from both changes.
> The plan is to to collect them and report back in the next few days.
> If we don't want to apply them without the performance data, then
> please consider this posting as RFC.
After spending some time on performance meas
Thanks for the hint! I was starting to get confused.
On Thu, Mar 19, 2015 at 01:50:31AM -0700, Andy Zhou wrote:
> It appears that I sent out some old patch files in error. Sorry.
>
> The set of 18 is the set for review. The set of 20 is an older set,
> please disregard them.
>
>
>
> On Thu, M
It appears that I sent out some old patch files in error. Sorry.
The set of 18 is the set for review. The set of 20 is an older set,
please disregard them.
On Thu, Mar 19, 2015 at 12:08 AM, Andy Zhou wrote:
> This patch set implements two ideas improve ovsdb connection scaling:
>
> * Allow mul
This patch set implements two ideas improve ovsdb connection scaling:
* Allow multiple jsonrpc connection to share a single ovsdb monitor, thus
maintaining a single set of changes.
* With in the same monitor, cache the json object generated for an update.
If the same update is requested by a
