Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #73720

Re: print statements and profiling a function slowed performance

X-Received by 10.42.39.140 with SMTP id h12mr16213071ice.9.1404008707125; Sat, 28 Jun 2014 19:25:07 -0700 (PDT)
X-Received by 10.50.61.145 with SMTP id p17mr430124igr.16.1404008707043; Sat, 28 Jun 2014 19:25:07 -0700 (PDT)
Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!hn18no17763577igb.0!news-out.google.com!gf2ni200igb.0!nntp.google.com!hn18no17763567igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups comp.lang.python
Date Sat, 28 Jun 2014 19:25:06 -0700 (PDT)
In-Reply-To <87wqc0hmdo.fsf@elektro.pacujo.net>
Complaints-To groups-abuse@google.com
Injection-Info glegroupsg2000goo.googlegroups.com; posting-host=59.95.7.105; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui
NNTP-Posting-Host 59.95.7.105
References <d5d8cea5-c4c9-42c4-865f-9efe33b162ed@googlegroups.com> <mailman.11266.1403810884.18130.python-list@python.org> <d1dbc61a-ed09-4a10-b4d5-deb40cb54430@googlegroups.com> <53acdd24$0$29985$c3e8da3$5496439d@news.astraweb.com> <lok45f$45v$1@ger.gmane.org> <CANc-5UxS9O=yPphCGzr=cbX-_SLTKLq28FbxwC2FVwLPrbqXqw@mail.gmail.com> <CALwzidnkQyeQ5qBawFj=6DYBTySHc9VAcTSno7i5pNbH8KKHFQ@mail.gmail.com> <CANc-5UxOUSPjKZhZzipGA9UUJr-R_Zq3vbfPFstQsdg4BBRGdg@mail.gmail.com> <mailman.11298.1403915364.18130.python-list@python.org> <87wqc0hmdo.fsf@elektro.pacujo.net>
User-Agent G2/1.0
MIME-Version 1.0
Message-ID <c7abf2ff-ae75-4ae2-979b-cb86ea746898@googlegroups.com> (permalink)
Subject Re: print statements and profiling a function slowed performance
From Rustom Mody <rustompmody@gmail.com>
Injection-Date Sun, 29 Jun 2014 02:25:07 +0000
Content-Type text/plain; charset=ISO-8859-1
Xref csiph.com comp.lang.python:73720

Show key headers only | View raw


On Sunday, June 29, 2014 12:50:19 AM UTC+5:30, Marko Rauhamaa wrote:
> Chris Angelico wrote:

> > Threading is a focus of so many myths. People who don't understand it
> > think that threads are magic pixie dust that fixes everything, or else
> > magic pixie dust that breaks everything. Or both, at the same time.
> > Neither notion is true.

> I'm in the latter camp.

> More precisely: threads have their uses but they are used far too much
> and not feared nearly enough.

Third Camp:
Since both views are true:

Chris: Threads solve a large class of important problems
Marko: Threads are horribly error prone

lets have a (bondage-and-discipline) language that supports smooth mostly
error-free threads.

Most famous recent example is Go.
More classic (and more bondage-and-discipline) are Erlang, CloudHaskell

PS. I find the success of node.js (async model) scary.
The success is a fact

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


Thread

print statements and profiling a function slowed performance CM <cmpython@gmail.com> - 2014-06-26 11:44 -0700
  Re: print statements and profiling a function slowed performance Michael Torrie <torriem@gmail.com> - 2014-06-26 13:14 -0600
    Re: print statements and profiling a function slowed performance CM <cmpython@gmail.com> - 2014-06-26 13:36 -0700
      Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-27 12:06 +1000
      Re: print statements and profiling a function slowed performance Michael Torrie <torriem@gmail.com> - 2014-06-26 19:59 -0600
      Re: print statements and profiling a function slowed performance Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-06-28 09:41 -0400
      Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-28 23:50 +1000
      Re: print statements and profiling a function slowed performance Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-06-29 02:14 -0400
      Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-29 17:14 +1000
  Re: print statements and profiling a function slowed performance Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-26 20:27 +0100
    Re: print statements and profiling a function slowed performance CM <cmpython@gmail.com> - 2014-06-26 13:37 -0700
      Re: print statements and profiling a function slowed performance Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-27 02:55 +0000
        Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-27 13:14 +1000
        Re: print statements and profiling a function slowed performance Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-27 16:55 +0100
        Re: print statements and profiling a function slowed performance Skip Montanaro <skip@pobox.com> - 2014-06-27 11:05 -0500
        Re: print statements and profiling a function slowed performance Ian Kelly <ian.g.kelly@gmail.com> - 2014-06-27 15:35 -0600
        Re: print statements and profiling a function slowed performance Skip Montanaro <skip@pobox.com> - 2014-06-27 19:12 -0500
        Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-28 10:29 +1000
          Re: print statements and profiling a function slowed performance Marko Rauhamaa <marko@pacujo.net> - 2014-06-28 22:20 +0300
            Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-29 09:30 +1000
            Re: print statements and profiling a function slowed performance Rustom Mody <rustompmody@gmail.com> - 2014-06-28 19:25 -0700
              Re: print statements and profiling a function slowed performance Chris Angelico <rosuav@gmail.com> - 2014-06-29 12:32 +1000
        Re: print statements and profiling a function slowed performance Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-28 02:06 +0100
  Re: print statements and profiling a function slowed performance Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-06-26 22:11 -0400

csiph-web