Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!newsfeed.straub-nv.de!news.glorb.com!news2.glorb.com!news-out.readnews.com!transit3.readnews.com!news-out.octanews.net!indigo.octanews.net!auth.beige.octanews.com.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.python Subject: Re: Python CPU References: <01bd055b-631d-45f0-90a7-229da4a9a362@t19g2000prd.googlegroups.com> <8vps7tF9vuU1@mid.individual.net> <4d97f125$0$29992$c3e8da3$5496439d@news.astraweb.com> <4d981eb5$0$10581$742ec2ed@news.sonic.net> <8vtbclF7q4U1@mid.individual.net> <4d9a2281$0$10524$742ec2ed@news.sonic.net> Date: Mon, 04 Apr 2011 13:20:15 -0700 Message-ID: <7xhbadojk0.fsf@ruckus.brouhaha.com> Organization: Nightsong/Fort GNOX User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:KL83smrr4dJyCuiFNs6ORbZs8b0= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 7 NNTP-Posting-Date: 04 Apr 2011 15:20:15 CDT X-Complaints-To: abuse@octanews.net Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:2593 John Nagle writes: > That sort of thing was popular in the era of the early > Cray machines. Once superscalar CPUs were developed, > the overhead on tight inner loops went down, and several > iterations of a loop could be in the pipeline at one time, Vector processors are back, they just call them GPGPU's now.