Open Stack

>Arguably if we're actually seeing performance issues then it's not a
distraction but rather a real problem that needs fixing.

The important take-away from the thread is that we aren't anywhere near
hitting python limits though. Our main bottleneck is due to the fact that
we are serializing all DB requests in a DB-heavy codebase.

On Mon, May 11, 2015 at 9:18 PM, Chris Friesen <chris.friesen at windriver.com>
wrote:

> On 05/11/2015 08:22 PM, Jay Pipes wrote:
>
>> c) Many OpenStack services, including Nova, Cinder, and Neutron, when
>> looked at
>> from a thousand-foot level, are little more than glue code that pipes out
>> to a
>> shell to execute system commands (sorry, but it's true).
>>
>
> No apologies necessary. :)
>
>  So, bottom line for me: focus on the things that will have the biggest
>> impact to
>> long-term cost reduction of our codebase.
>>
>
> +1
>
>  So, to me, the highest priority performance and scale fixes actually have
>> to do
>> with the simplification of our subsystems and architecture, not with
>> whether we
>> use mysql-python, PyMySQL, Python vs. Scala vs. Rust, or any other
>> distractions.
>>
>
> Arguably if we're actually seeing performance issues then it's not a
> distraction but rather a real problem that needs fixing.
>
> But I agree that we shouldn't be trying to optimize the performance pf
> code that isn't causing problems.
>
> Chris
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150511/12f54f3a/attachment.html>