Re: [ovs-dev] [PATCH 2/3] Add optional C extension wrapper for Python JSON parsing

2016-06-08 Thread Ben Pfaff
On Wed, Jun 08, 2016 at 08:55:14AM -0500, Terry Wilson wrote: > The pure Python in-tree JSON parser is *much* slower than the > in-tree C JSON parser. A local test parsing a 100Mb JSON file > showed the Python version taking 270 seconds. With the C wrapper, > it took under 4 seconds. > > The C ext

[ovs-dev] [PATCH 2/3] Add optional C extension wrapper for Python JSON parsing

2016-06-08 Thread Terry Wilson
The pure Python in-tree JSON parser is *much* slower than the in-tree C JSON parser. A local test parsing a 100Mb JSON file showed the Python version taking 270 seconds. With the C wrapper, it took under 4 seconds. The C extension will be used automatically if it can be built. If the extension fai

Re: [ovs-dev] [PATCH 2/3] Add optional C extension wrapper for Python JSON parsing

2016-06-07 Thread Ben Pfaff
On Tue, May 31, 2016 at 07:14:51PM -0500, Terry Wilson wrote: > The pure Python in-tree JSON parser is *much* slower than the > in-tree C JSON parser. A local test parsing a 100Mb JSON file > showed the Python version taking 270 seconds. With the C wrapper, > it took under 4 seconds. > > The C ext

[ovs-dev] [PATCH 2/3] Add optional C extension wrapper for Python JSON parsing

2016-05-31 Thread Terry Wilson
The pure Python in-tree JSON parser is *much* slower than the in-tree C JSON parser. A local test parsing a 100Mb JSON file showed the Python version taking 270 seconds. With the C wrapper, it took under 4 seconds. The C extension will be used automatically if it can be built. If the extension fai