Re: Nested loops is strangely slow, totally at a loss.

References	<20141210052025.GA84184@FuzzyHorror> <CAPTjJmrM_nrGhPn2Le7b0iDOL5V035SOE3kVg98_89dVjueynA@mail.gmail.com>
From	Ian Kelly <ian.g.kelly@gmail.com>
Date	2014-12-10 00:13 -0700
Subject	Re: Nested loops is strangely slow, totally at a loss.
Newsgroups	comp.lang.python
Message-ID	<mailman.16799.1418195682.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Dec 9, 2014 at 11:30 PM, Chris Angelico <rosuav@gmail.com> wrote:
> Are you sure it isn't? Your 'space' is an iterable cubic
> cross-product. Your first loop checks (0,0,0) which is the first
> element returned, and is thus fast... but it also *consumes* that
> first element. The next time you test it, the entire space gets
> consumed, looking for another (0,0,0), which won't exist. That means
> iterating over 580**3 == 195112000 (two hundred million) tuples, and
> that *is* going to be slow.

Huh, I wasn't even aware that membership tests worked on iterables with no
__contains__ method. Seems odd to me that 'x in y' should be supported but
not 'len(y)'.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Nested loops is strangely slow, totally at a loss. Ian Kelly <ian.g.kelly@gmail.com> - 2014-12-10 00:13 -0700

csiph-web