On 9/5/07, Paul Johnston [EMAIL PROTECTED] wrote:
data. I did some benchmarks a while back to see how everything
stacked up as I was wondering if I was doing everything the hard way
(in C++) instead of using SqlAlchemy, etc. TurboEntity is the same as
Great work Eric.
I am quite
since performance is the hot topic these days, I thought Id note that
I've made some ORM improvements in the current SQLAlchemy trunk. We
have a profiling test that loads 10 objects each with 50 child
objects, eagerly loaded across 500 rows. Version 0.3.10 uses 70040
function calls,
I am quite surprised at the results. I would have thought
ActiveMapper/TurboEntity would only be marginally slower than plain
SQLAlchemy. And again, I'm surprised that SA is faster than MySQLdb. How
does that work out? I though SA used MySQLdb??? Your use of query cache
and best of three
Hi,
data. I did some benchmarks a while back to see how everything
stacked up as I was wondering if I was doing everything the hard way
(in C++) instead of using SqlAlchemy, etc. TurboEntity is the same as
Great work Eric.
I am quite surprised at the results. I would have thought
On 9/4/07, Acm [EMAIL PROTECTED] wrote:
I am trying out Elixir 0.3.0 over SQLAlchemy 0.3.10 in a Python 2.5
environment.
Are there any known performance issues with Elixir for CRUD (Create
Select Update Delete) commands?
Not that I know of. There shouldn't be any overhead (over raw