In case it helps, I've also seen this CPU eating problem. I'm using:
REPL-y 0.1.9 Clojure 1.5.1. I don't know what you guys mean by MBP and MBA.
--mark
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
MBP = Mac Book Pro
MBA = Mac Book Air
On Sat, Jan 25, 2014 at 9:12 PM, greybird m...@greybird.com wrote:
In case it helps, I've also seen this CPU eating problem. I'm using:
REPL-y 0.1.9 Clojure 1.5.1. I don't know what you guys mean by MBP and MBA.
--mark
--
--
You received this
MBP -- Mac Book Pro
MBA -- Mac Book Air
Best,
Jarrod
On Saturday, January 25, 2014 11:12:37 PM UTC-5, greybird wrote:
In case it helps, I've also seen this CPU eating problem. I'm using:
REPL-y 0.1.9 Clojure 1.5.1. I don't know what you guys mean by MBP and MBA.
--mark
--
--
You
On Wed, Jan 22, 2014 at 5:29 PM, John Chijioke johnben...@gmail.com wrote:
Not true. More RAM, more power.
Why?
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from
It's not true. All memory has to be kept active at all times. Now you may
experience less battery usage due to the GC having to run more often, but
that's not exactly a memory usage problem.
Not to mention that the OS will almost always use all free ram for disk
caches and the like.
On Sat,
Not true. More RAM, more power. If it hits swap, even more power. That has
been my personal observation.
On Monday, January 20, 2014 6:53:14 AM UTC+1, g vim wrote:
On 20/01/2014 05:43, john walker wrote:
The JVM hasn't been receiving the love it deserves lately! Fortunately,
percent
On Sunday, January 19, 2014 11:19:45 PM UTC-6, g vim wrote:
critical factor. I'm not sure I can work outside Leiningen, though. It
seems to be as much a part of the Clojure development process as anything.
Just to be clear, Leiningen only eats CPU when started in an arbitrary
directory.
On Jan 20, 2014, at 11:14 , Mars0i marsh...@logical.net wrote:
Just to be clear, Leiningen only eats CPU when started in an arbitrary
directory. When started from a Leiningen project directory, it doesn't use
CPU unless I tell it to. I have not investigated what it is in the project
No, didn't see it as a real problem.
Odd. Just checked my MBP, and the CPU-eating behavior doesn't occur on
mine either. Only on the MBA. Both with Leiningen 2.3.4 and Java
1.6.0_65, and same OS (10.6.8--I don't upgrade OSes often). I'll have to
check whether there's something different
Is it likely that a typical Clojure development environment:
- LightTable instarepl
- Luminus web app running within `lein ring server`
will consume significantly more battery power than a typical Rails
environment:
- Vim
- Rails app running within `rail server`
It's just that I've
One thing that will totally kill MBP batter performance is if the system
decides do kick over to dedicated graphics. I highly recommend this app:
http://gfx.io/ It'll put an icon in the top right of your screen that shows
which GFX card is in use. On my 2012 MBP I get about 6 hours of life on the
Good points about the graphics, Tim. Do you have any idea if the JVM's
RAM requirement in itself takes more power from the system than
developing, say, a Rails app in Vim? One pisser with my new-ish Macbook
Pro is there's no such thing as a spare battery.
gvim
On 20/01/2014 03:47, Timothy
fwiw, there is the option of developing Clojure in vim. That's what I
prefer at present--but everyone's needs and preferences are different.
(Also, probably not relevant, but I noticed that 'lein repl' eats up CPU
even when it's not doing anything, if I start it in a directory without a
On 20/01/2014 04:37, Mars0i wrote:
fwiw, there is the option of developing Clojure in vim. That's what I
prefer at present--but everyone's needs and preferences are different.
(Also, probably not relevant, but I noticed that 'lein repl' eats up CPU
even when it's not doing anything, if I start
The JVM hasn't been receiving the love it deserves lately! Fortunately,
percent memory usage isn't going to have any effect on battery life until
you hit swap. The resources you should consider are just activity on the
cpu/gpu/disk.
So yeah, it's light table. It's not its fault for being
On 20/01/2014 05:43, john walker wrote:
The JVM hasn't been receiving the love it deserves lately! Fortunately,
percent memory usage isn't going to have any effect on battery life
until you hit swap. The resources you should consider are just activity
on the cpu/gpu/disk.
So yeah, it's light
16 matches
Mail list logo
