delta/python-packages/sqlalchemy.git/test/aaa_profiling, branch fix_mariadb102_default

Isolate memory tests in forks

2017-08-14T16:41:58+00:00

Swing the biggest hammer, run multiprocessing.Process() for
each memusage test individually so that they are fully isolated
from the parent process and any side effects of pytest-xdist

Also add --nomemory as a shortcut to exclude_tags=memory-intensive
and add this to the setup.py test runner as the memory tests
should not be running for quick runs

Change-Id: I3c16c781e21b33deb939a64e77a6e0e41fb86922

- try adding the prints back in and re-test

2017-08-11T13:54:16+00:00

Change-Id: I3a82b06ecc3c065240cc05871dee2881f20e414e

- take more print statements out, maybe this is not

2017-08-10T19:46:37+00:00

the issue
- unblock pytest-xdist now that the upstream issue is fixed,
maybe this old version is the issue

Change-Id: I28dd7ae0872948a188651d42e2f4af60bcbafe81

- dont print samples, this appears like it may be

2017-08-08T21:24:23+00:00

itself causing the memory leak in conjunction with pytest-xdist

Change-Id: Ia8704e54186e6dd60ea0e32a246fcf1419686663

- allow the shrink phase for memusage to go until zeroed,

2017-08-08T18:02:16+00:00

some MySQL-env element is causing memory growth that goes very
far before stopping

Change-Id: Ic0882dd78636067980fceba4e3a969de78d5b26a

Add selectin loading

2017-04-26T20:08:57+00:00

Adding a new kind of relationship loader that is
a cross between the "immediateload" and the "subquery"
eager loader, using an IN criteria to load related items
in bulk immediately after the lead query result is loaded.

Change-Id: If13713fba9b465865aef8fd50b5b6b977fe3ef7d
Fixes: #3944

Use baked lazyloading by default

2017-04-13T18:22:59+00:00

The ``lazy="select"`` loader strategy now makes used of the
:class:`.BakedQuery` query caching system in all cases.  This
removes most overhead of generating a :class:`.Query` object and
running it into a :func:`.select` and then string SQL statement from
the process of lazy-loading related collections and objects.  The
"baked" lazy loader has also been improved such that it can now
cache in most cases where query load options are used.

Change-Id: Ic96792fffaa045ae9aa0a4657d6d29235d3efb85
Fixes: #3954

- try one more test, then we're likely going to give up on cx_Oracle

2017-04-12T19:28:05+00:00

Change-Id: I7f9a1265664b0368ee7a771d01c7ca1612156d1f

- move a few memusage tests out of "backend". something is up w/ cx_Oracle

2017-04-12T19:15:16+00:00

when the suite runs, such as a background thread or something like that,
which is affecting these tests a bit.

Change-Id: I52d50a44778ec1eecb8e335ae59b1a4773e80a79

Warn on _compiled_cache growth

2017-04-12T16:53:40+00:00

Added warnings to the LRU "compiled cache" used by the :class:`.Mapper`
(and ultimately will be for other ORM-based LRU caches) such that
when the cache starts hitting its size limits, the application will
emit a warning that this is a performance-degrading situation that
may require attention.   The LRU caches can reach their size limits
primarily if an application is making use of an unbounded number
of :class:`.Engine` objects, which is an antipattern.  Otherwise,
this may suggest an issue that should be brought to the SQLAlchemy
developer's attention.

Additionally, adjusted the test_memusage algorithm again as the
previous one could still allow a growing memory size to be missed.

Change-Id: I020d1ceafb7a08f6addfa990a1e7acd09f933240