iPulse is a system monitoring application that lets you peek at the inner workings of Mac OS X through a clever and visually compact user interface. Using iPulse's customizable gauges, users can monitor system activity such as CPU and memory usage, free disk space, network activity and more. However, unlike other OS X monitoring apps, iPulse takes up minimal screen real estate, and does so with a unique, informative and visually pleasing user interface.
What's New
Version 2.5.2:
- Added support for OS X 10.9 (Mavericks)
Requirements
- Intel, 64-bit processor
- OS X 10.4 or later
(19)
(21)
Displaying 1-10 of 30
-
-
-
iPulse is a system monitoring application that lets you peek at the inner workings of Mac OS X through a clever and visually compact user interface. Using iPulse's customizable gauges, users can monitor system activity such as CPU and memory usage, free disk space, network activity and more. However, unlike other OS X monitoring apps, iPulse takes up minimal screen real estate, and does so with a unique, informative and visually pleasing user interface.
+25
Fabro reviewed on 16 Aug 2012
I have used MenuMeters (free but lacks some features) and iStatMenus (useful and with a plethora of features and options, but too resource-intensive).
If only iPulse could show a graph with the history of my network interfaces utilization into its Info window...
+115
see this http://bit.ly/PMusGA
+25
These options are disabled by default and may be the cause of the inaccuracies you are reporting.
+1
+115
Regardless of "who" was responsible prior, when running iPulse the lockups would occur. When not running iPulse, no lockups. It may have been a buggy call back to Mac OS X or just a poor implementation of that call in the shareware.
iPulse now *appears* to be a better citizen. Is the problem gone, time and usage will tell.
+17
"You are now prompted for a password each time you launch iPulse on Snow Leopard"
Why can't it remember the setting? Why do I need to enter a password every time I start iPulse? Apple's "Activity Monitor" does not prompt the user for a password every time it is started.
If it can't be fixed because there are inherent problems with the way that iPulse is implemented, then that security vulnerability should be addressed and fixed rather then creating a huge inconvenience for the users.
This change means that I can no longer have iPulse as a startup item has I have for years.
+1
+170
It is Apple who has broken a working thing again and as usual, Apple users instead of asking "Why are you breaking?", they blame the little shareware vendor instead.
iPulse has ZERO connection ability to network, including local network so it is not insecure in any way. Please don't claim such absurd things while you apologize for Apple.
The root of issue is: Apple doesn't give a s**t to "little guy" or third party vendors while they design/implement OS upgrades. Fascistically removing third party component support from Quicktime X, removal of Input Manager functionality, not implementing Carbon 64bit last second and announcing it at iPod event. Let me continue?
+115
Cerniuk reviewed on 01 Jun 2009
iPulse will check the mounted volumes (hard drives) including remote server volumes periodically to update the usage status. When it does this and the volume is no longer available, it will not time out nor release the query call for disk usage statistics.
Here is the scenario: You are at work and you have a server mounted. Maybe it is your Windows NT corp server, Mac OS X corp server, your iDisk cloud server, or your TimeCapsule volume. You close the lid to sleep the Mac and it sleeps. Pack it in your bag, jet for the door. You then later open your Mac (on the train, at home, etc.) and you have no network connection or a different network connection that does not allow you to get to one of the servers that you were connected to before. iPulse will go brute force against that server asking for statistics and not let go. That server volume appears busy and the Finder cannot let go either. You establish an Internet connection (wifi, ethernet, cell modem, etc) and now nothing seems to be able to talk to the network even though you do have a connection as verified by the Network Preferences in your System Preferences. Then you check your process list (command-option-escape) and note that iPulse is not responding. You figure, ok, just kill it but that thing is a vampire and drains your network connection dry and cannot be killed. Kill Kill Kill, nope nope nope. Then you see your Finder go non-responsive. Kill, nope. Other processes, as they access network resources start to go red including iChat, Pages (oops, update check...) and others. Some kill, some do not. You try launching network utilities that just seem to bounce indefinitely (they are trying to open network connections and the network stack is gridlocked by iPulse, sorry charlie)
Ok, long story short, your Mac is Tango Uniform, time for the three key salute: command-control-power. This time you take iPulse **out** of your login items and come and write a lengthy review about one of your favorite little utilities becoming more pain that it is worth. Sad Monday, lost an old friend.
+12
JJ990 reviewed on 17 Apr 2009
+1
+1
Sans reviewed on 05 Apr 2007
+124
Lee123 reviewed on 05 Apr 2007
+1
+1
+43
mr kitty reviewed on 23 Nov 2006
went straight in to the trash.
+65
Tddisc rated on 19 Apr 2012