Abnormal long CMS GC cycles

SunOS 5.10
JDK 1.4.2_09
-J-d64 -J-server -J-Xms500m -J-Xmx1800m -J-XX:-UseTLAB -J-Xss1m -J-XX:+PrintGCDetails -J-XX:+PrintGCTimeStamps -J-XX:+UseConcMarkSweepGC -J-XX:-CMSParallelRemarkEnabled
We have severale too long CMS GC cycles that looks abnormal. First of this type:
10892.825: [GC 10892.826: [ParNew: 8063K->0K(8128K), 0.7424865 secs] 1821348K->1814357K(1843136K), 0.7427192 secs]
10893.818: [GC 10893.819: [ParNew: 8064K->8064K(8128K), 0.0000434 secs]10893.819: [CMS10895.444: [CMS-concurrent-preclean: 23.824/82.681 secs]
: 1814357K->1381716K(1835008K), 23.5543968 secs] 1822421K->1381716K(1843136K), 23.5547208 secs]
10917.630: [GC 10917.630: [ParNew: 8063K->0K(8128K), 0.0895837 secs] 1389780K->1384614K(1843136K), 0.0897894 secs]
10917.723: [GC [1 CMS-initial-mark: 1384614K(1835008K)] 1384633K(1843136K), 0.0102144 secs]
10917.733: [CMS-concurrent-mark-start]
10918.356: [GC 10918.356: [ParNew: 8063K->0K(8128K), 0.0500847 secs] 1392678K->1386366K(1843136K), 0.0503327 secs]Second of this:
6867.181: [GC 6867.181: [ParNew: 8064K->0K(8128K), 0.0914768 secs] 1215305K->1208597K(1843136K), 0.0916873 secs]
6868.095: [GC 6868.095: [ParNew: 7710K->0K(8128K), 0.0602197 secs]6868.155: [CMS[Unloading class sun.reflect.GeneratedConstructorAccessor22]
[Unloading class sun.reflect.GeneratedMethodAccessor47]
[Unloading class sun.reflect.GeneratedMethodAccessor52]
[Unloading class sun.reflect.GeneratedMethodAccessor49]
[Unloading class sun.reflect.GeneratedMethodAccessor58]
[Unloading class sun.reflect.GeneratedMethodAccessor54]
[Unloading class sun.reflect.GeneratedConstructorAccessor7]
: 1211951K->909368K(1835008K), 15.7549920 secs] 1216308K->909368K(1843136K), 15.8155357 secs]Is it know JDK bugs, or some missconfiguration?

The presence of the "(System)" in the full GC line means that that collection was caused by a call to System.gc(). You can try running with "-XX:+DisableExplicitGC" as tschodt suggests, but that may have detrimental effects if something thinks it needs a full collection after an hour.
Are you using something like Java RMI, which needs a collection every once in a while to maintain its distributed garbage collection algorithms. You can change the interval at which RMI calls System.gc(), and you can get it to just start a CMS cycle instead of causing a full compacting collection.

Similar Messages

Im running a web-based CMS, that cycles through a number of pages, and wanted to know if there is an auto reload code option ( not plug-in ) that can restart previous page when connection failed.

I am running a web-based CMS that cycles through a number of pages, each for different times ( ranging from 40 seconds to 2 minutes )and is displayed in a number of shops. Every now and then our internet drops, and the page errors with connection failed. I’m wondering if there is anyway to auto reload the page as soon as the error connection failed is showing. auto-reload addon is not an option as this will interrupt the sequence.
The following error was encountered: 
 
<ul><li>Connection Failed</li></ul> 
 
This means: 
 
<pre>

I am running a web-based CMS that cycles through a number of pages, each for different times ( ranging from 40 seconds to 2 minutes )and is displayed in a number of shops. Every now and then our internet drops, and the page errors with connection failed. I’m wondering if there is anyway to auto reload the page as soon as the error connection failed is showing. auto-reload addon is not an option as this will interrupt the sequence.
The following error was encountered: 
 
<ul><li>Connection Failed</li></ul> 
 
This means: 
 
<pre>

Construction of a new ServerSocket taking abnormally long - ipv6-related

SUMMARY
It takes 180+ seconds to open a ServerSocket if IPv6 is present on the loopback device.
SYSTEM
Debian unstable
Linux desktop3.mgn 2.4.27-speakup #1 Fri Feb 25 15:43:38 EST 2005 i686 GNU/Linux
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
MORE INFO
Last place within PlainSocketImpl everything's alright is /**
 * Load net library into runtime.
 static {
 java.security.AccessController.doPrivileged(
 new sun.security.action.LoadLibraryAction("net"));
 initProto();
 }After the call to initProto (which is a native method) it takes 180+ seconds for the last connect() call below (got i from running strace) to timeout:socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 5
listen(5, 1) = 0
getsockname(5, {sa_family=AF_INET6, sin6_port=htons(37753), inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 6
connect(6, {sa_family=AF_INET6, sin6_port=htons(37753), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=3221214872}, 24) = -1 ETIMEDOUT (Connection timed out)TEST PROGRAMimport java.net.*;
public class Test {
 public static void main(String[] args) {
 try {
 long start = System.currentTimeMillis();
 ServerSocket serverSocket = new ServerSocket(4445); // <-- this is what takes abnormally long
 long stop = System.currentTimeMillis();
 System.out.println("stop - start = " + (stop - start));
 } catch (UnknownHostException e) {
 e.printStackTrace();
 System.exit(-1);
 } catch (java.io.IOException e) {
 e.printStackTrace();
 System.exit(-2);
}CASE "ON"# ip a show dev lo
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 inet6 ::1/128 scope host
$ java Test
stop - start = 189011CASE "OFF"# ip a del ::1/128 dev lo
# ip a show dev lo
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
$ java Test
stop - start = 18Commands executed to "turn ipv6 on/off":ip a del ::1/128 dev lo
ip a add ::1/128 dev loNo other programs show this delay. Is this a bug?

I think so, I've read something like that in BugParade.
Try Java5 or Java6 (Mustang) with your code.
--Marc

LDAP Query from Java taking abnormally long

Is there any reason why this query would take an abnormally long time? When I run the query from the command line it comes back practically instantly, but when I access it via Java it takes close to 30 seconds.
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.NamingEnumeration;
import javax.naming.NamingException;
import javax.naming.directory.Attribute;
import javax.naming.directory.Attributes;
import javax.naming.directory.DirContext;
import javax.naming.directory.InitialDirContext;
import javax.naming.directory.SearchControls;
import javax.naming.directory.SearchResult;
public class LDAPTest {
      * @param args
     public static void main(String[] args) {
          String username = System.getProperty("user.name");
          String LDAPServer = "ldap://ldap.myldapserver.net/";
          //String attribute = "";
          String query = "uid=" +username;
          Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
        env.put(Context.PROVIDER_URL, LDAPServer);
        DirContext context = null;
        NamingEnumeration enumeration = null;
          try {
               context = new InitialDirContext(env);
            SearchControls ctrl = new SearchControls();
            ctrl.setSearchScope(SearchControls.SUBTREE_SCOPE);
            enumeration = context.search("", query, ctrl);
            //while (enumeration.hasMore()) {
                 SearchResult searchResult = (SearchResult) enumeration.next();
                Attributes attributes = searchResult.getAttributes();
                Attribute attr = attributes.get("cn");
                String cn = (String) attr.get();
                System.out.println(" Person Common Name = " + cn);
        } catch (NamingException e) {
            throw new RuntimeException(e);
        } finally {
            if (enumeration != null) {
                try {
                     enumeration.close();
                } catch (Exception e) {
            if (context != null) {
                try {
                     context.close();
                } catch (Exception e) {
}

njb7ty wrote:
One way to speed it up is to only retreive those attributes your interested in via ctls.setReturningAttributes.
Also, if you know what sub directories you want to look in, you can create a list of just those subdirectories and look through them one at a time via ctls.setSearchScope(SearchControls.ONELEVEL_SCOPE);
SearchControls ctls = new SearchControls();
ctls.setReturningAttributes((String[])attrIDs.toArray(new String[attrIDs.size()]));
//only look at the immediate folder level specified (not in sub-folders)
ctls.setSearchScope(SearchControls.ONELEVEL_SCOPE);Hi, thanks. I tried these, unfortunately I don't know enough about ldap to set the onelevel_scope properly. I have narrowed it down as a combination of load and login issues. For example, in our test environment the java program returns instantly with anonymous. In our production environment it returns in about 30-40 seconds with no login credentials supplied. (it does allow anonymous access). I made sure I set the authentication to none when attempting to try this. But when I do an anonymous query from the command line via a ldapsearch program it pulls the results instantly. (i know it is anonymous because if I specify credentials it pulls back additional data). For some reason it just takes really long to resolve in our production environment if I try anonymous access and I haven't figured it out yet. When I supply login credentials to our production environment it comes back in under a fifth of a second.

Office 2007 saving documents over mapped network drive takes abnormally long

On a new Windows 8.1 Pro 64 bit computer, I have installed Office 2007. When I attempt to save documents to a mapped network drive on a peer network (saving to a Windows 8.1 Pro 64 bit computer), I have abnormally long save times. However, when I attempt
to save documents to my computer, I have no issues. I do not have any issues when opening the files over the mapped drive.
Turning off the third-party Bullguard Internet Security antivirus and firewall makes no difference. Setting as an exception the excluded mapped drive folder makes no difference either.
I have disconnected the mapped drive and re-mapped the network drive, but this makes no difference.
I had no problem with the same software on a prior computer running the same Office 2007 version. Another computer on the network has no issues either.
Please advise how to speed up the saved documents (Word, Excel).

Hi,
As the slow to save files issue, please try the suggestion below to modify the registry:
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the
registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,
http://windows.microsoft.com/en-US/windows7/Back-up-the-registry
To start the Registry Editor, press Win + R, type "regedit.exe" in the blank box, press Enter. Then add the following registry key to the machine:
[Hkey_Current_User\Software\Microsoft\Office\12.0\Word\Options]
"DisableRobustifiedUNC"=Dword:00000001
[Hkey_Current_User\Software\Microsoft\Office\12.0\Excel\Options]
"DisableRobustifiedUNC"=Dword:00000001
I hope this can help.
Regards,
Melon Chen
TechNet Community Support

Abnormally long RAM Preview startup?

Something has happened in with my AE 9.0.2 / Mac OS X 10.5.7 that it's taking a very long time for RAM Previews to begin building. I'm talking 30 seconds or more each time I press "0" on my numeric pad. This is on both complex projects or very simple projects.
The Info palette tells me "Background Process Status: Loading Projects...." before it starts to render frames.
Any ideas what's causing this?

What Mylenium says is true: Once the background processes start up to take part in Render Multiple Frames Simultaneously multiprocssing, they should stay active until you quit After Effects...
> Yup, of course I'm using multi-processing.
There is one big caveat, though:
If you have turned on Render Mutliple Frames Simultaneously, but the background processes don't have enough RAM to render your frames, then they'll just shut back down again. And then they'll try to start the next time that you do a render (including render for previews). And then they'll just shut back down again. All of this wastes precious time.
The moral of the story: Don't think that checking the Render Multiple Frames Simultaneoulsy checkbox is the right thing to do in all cases. That's why it's an option, and that's why it defaults to being off. And make sure that you aren't starving the background processes of RAM.

How long is an 'abnormally long' time to boot after 10.4.8 update?

How long is too long to wait for my macBook Pro to take to boot up after installing the latest update?
An hour?
2 hours?
A day?
I installed from Automatic Updates and shutdown rather than restart. Came abck hours later turned on powerer and waited and waited. After about an hour I tunred it off booted from the install CD, ran the disk utility, fixed a few permission and rebooted...
Should I take it in to the Apple Store tomorrow morning if this continues or reinstall the OS and start over?

Hello dn:
As an aside, comparing Windows to OS X is like
comparing a plow horse ready for the glue factory to
a thoroughbred race horse. I use both every day and
have for years, so I have vivid daily comparisons.
Now then, as I indicated above, you probably caused
the problem by interrupting the software update
process. At a guess, you have clobbered directories
(you, not Apple). The first step would be to run
repair disk from your software install DVD (boot it,
holding down the "C" key). Repair disk is found in
the disk utility. If that works, you should be back
to the point where you can reinstall the combo
updater. There is also an excellent third party
program (mentioned above) called DiskWarrior (pricey
at about $90, but worth it if it saves the day).
If none of that works, you probably should do an
archive and install:
http://docs.info.apple.com/article.html?artnum=107120
A good back up/retreat strategy is just good
computing practice whether or not you are a computing
professional. There are several approaches. I make
bootable clones of all my iMacs on an external
firewire drive using a little program called
SuperDuper (&28 at www.shirt-pocket.com). The
bootable clone gives me almost complete protection
against hardware or software problems.
By the by, these forums are user-to-user. Everyone
is a volunteer - not an Apple employee. Apple
monitors/moderates the forums and provides an
excellent resource. If you are new to Macs (as your
post seems to indicate), you should spend some time
browsing the forums and using the tools available -
including the excellent library of knowledge base
articles.
Barry
OK, So I'm a cry baby.
But I do not buy your argument that it was all my fault. After I inrterupted the hour ling gray screen and ran and fixed a few previlige problems and tried again over 2 hour went by with nothing but the gray screen.
Archive and intall did get me back and running, but by now 4 -5 hours of my life are gone that I want back!
And the tone on this whole board seems to be we MacBook owners, who unsupectingly trusted Apple and let the Automaitic Software Update have its way with a computer that was functioning just fine, the result of which is a computer that needs to have the OS reinstalled, are at fault for having poor prior knowledge?
I bring up Microsoft because they are BAD. They have an OS that allows 3rd parties to install code to render your computer useless at best, a robot of evil at worst.
Yet here we have the Apple, a trusted known entity and the manufacture of not only the hardware but the OS handing us an install that should have just WORKED.
So al I can think is the Delta install is the culprit, since I had previously been on 10.4.7 and the Archive & Install put in 10.4.6. The Combined installer is ok.
Again MacBook owners are victimized for keeping current?
Some one at Apple deserves a dummy slap at least.
MacBook owners represent the "Switchers". They bought on style and a promis of stability and reliability. Not the allure of becoming UNIX Geeks or even Uber User or browsers of forums. They came from that dull gray world out there where viruse roam but if you let automatic updates run and loaded up with antiv virus and spyware scanners, things pretty much worked.
I'm not new to mac as I have been usinge them since I shelled out $3,500 for a Mac SE. (Don't laugh). I gave up however being a Uber User and I at least am tenaciouse enought to find this discussion board. I suspect there are going to be a lot of busy Mac "Geniouses" for the next few days as ordinary computer users stream in with MacBooks with gray screens.
You know Sony support totally *****, but they are rated the best on the PC side for customer satisfaction. Why? You almost never have to seek support from Sony.
Again I'm just ******** 'casue it happend to me on a new laptop that was bone stock. Its working now so problem solved.

My app taking an abnormally long time to download.

I'm trying to download "Grand Theft Auto: San Andreas" and it is taking REALLY long to download, it's been about two days. Anything that could help it?

If you go into the Purchases page of the App Store you should be able to monitor progress. If there is none, try quitting, maybe even restarting the Mac to force the session to close, then try to download again thru the Purchases page. There will be no charge as the initial download did not conclude successfully.

Abnormally Long HDV Project Load Time with CS3

I have a relatively small HDV project, about 30 clips captured with HDVSplit. I find that after the CS3 splash screen goes by and while the project loading progress panel is displayed it takes about 2.5 minutes for the project work space to appear. Everything seems to work fine once the work space is displayed re: CS3 editing functionality.
Has anyone else run into this slow loading problem? Any suggestions as to what may be causing this? The clips are relatively short and the entire sequence on the timeline is less than 15 min.

For Pete's Sake man!
I am new here and there seems to be a few guys that have their heads so far up Adobe's *** that you do not see what you are saying.
I understand Howards frustration.
You people think that everyone must go out and buy All of Adobe's Products. To assume any person must be forced to buy a program they do not want or cannot afford is plain rude and obnoxious.
We are not all professionals like some of you, some of do actually shoot weddings, like myself. Why the heck must I buy more programs than I need (although I won After Effects Already)!!?? If you are all so professional why are you on these forums instead of making features in Hollywood? Dammit I get so upset by some people.
You leave people hating Adobe and their products. I have been reading this forum for about a day now and there is a common pattern. A guy will have a problem, 2 people will complain that he posts on the forums, 3 people will tell him to get rid of his camera, 4 will say buy After Effects or go buy this plugin. It is ridiculous! You are people are insane.
Final Cut Studio is by far a better option, you buy it and it works straight out of the box, no plugins no go buy another application. I am not an Apple supporter is hater, it seems that everyday I struggle with Adobe is one day I consider moving my business to Apple and Final Cut.
Premiere Elements is for kids. I wanted a professional editng program that was able to do it all in one, Adobe seemed to offer this.
Let us think about for a minute lads. It is either PC or Mac, Mac has good points but the initial investment is quite large so let us put it aside for now. PC. What editing software is there for PC. Sony Vegas, Premiere, AVID, Edius, Avid Liquid/Pinnacle, Ulead, Movie Maker, Power Director/Producer, and various others. So what do you chose....
Vegas, just does not have it all you know
Avid Liquid, again it's a bit for beginners
Avid, wow too bg for the guy starting out,
Premiere, the best pick of the bunch,
the rest are for kids and real amateurs.
Buw wait Premiere cannot function on it's own, it needs a plugin to this and a plugin to do that, it forever needs plugins. The only thing it is good for is just SD. I want to edit HD or HDV in Premiere I must go buy Cineform, what a load of crap. I want to do basic little effects,go buy After Effects, I want to colour Grade, go buy this or that plugin.
The cost of Premiere is fairly good, but before you can use it you need to buy After Effects (for effects simple and advanced), Photoshop (for titles), Cineform (well to edit anything actually and to support formats and proper 1920 x 1080 HD 4:4:4 uncompressed), and add that all up and it costs a shitload.
So that leads us back to Final Cut Pro where it all makes sense. You buy one G5, and one Final Cut Studio and it gets the job done all in one wonder. NOBODY OUT THERE CAN ARGUE WITH THE BENEFIT OF THAT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11
Now this entire post was pointless since I know everyone out there could not wait to get to the end just they could quote me and argue. You reading this did not even bother to see it from an objective point of view, I know for a fact. Whilst reading you were not listening. So this post was pointless, because nobody will STILL get it.
Disgruntled Adobe End user. I am returning CS3 back to Adobe for a refund.

My battery needs service as it is not working for long. Apple claims it is not a defective battery and that it is my fault since I had the computer for 2 1/2 years and have only run the battery down to empty 100 times. It is my fault because I did no

Con't
Apple claims that because I did not drain my battery frequently and kept it plugged in for extended periods of time, that it is my fault the battery is failing. I disagree because I was not ever told to consistently drain my battery before recharging or not to keep it on and plugs in for extended periods of time. I do keep my desktop computer on most of the time and that is why I have kept my Macbook air on for extended time periods. I feel that Applecare should cover this battey issue and not charge me for replacing the battey. I feel I should have been told to not keep my computer consistently running on with poweror the battery will fail. Has anyone had this problem? Apple should replace my battery under Apple care as my battery does not keep a charge anymore.
I'll wait to hear.

You said---Apple claims that because I did not drain my battery frequently
You said--- I was not ever told to consistently drain my battery before recharging
You should never do that on purpose, whoever told you that had it wrong or you misunderstood something
Sure you dont have that backwards? thats exactly what you DONT want to do.
Did you often drain the battery very low? that would explain a lot.
Someone might have been misinformed about "battery calibration" regarding much older Macs with removable batteries (see bottom)
You said-----I do keep my desktop computer on most of the time and that is why I have kept my Macbook air on for extended time periods.
thats a problem there, youre not supposed to do that.
Keeping batteries connected to a charger ensures that periodic "top-ups" do very minor but continuous damage to individual cells, hence Apples recommendation above:   “Apple does not recommend leaving your portable plugged in all the time”, …this is because “Li-ion degrades fastest at high state-of-charge”.
                    This is also the same reason new Apple notebooks are packaged with 50% charges and not 100%.
http://www.apple.com/batteries/notebooks.html
"Apple does not recommend leaving your portable plugged in all the time."
*If you don’t plan on using it for a few hours, turn it OFF (plugged in or otherwise) ..*You don’t want your Macbook both always plugged in AND in sleep mode       (When portable devices are charging and in the on or sleep position, the current that is drawn through the device is called the parasitic load and will alter the dynamics of charge cycle. Battery manufacturers advise against parasitic loading because it induces mini-cycles.)
Keep it plugged in when near a socket so you keep the charging cycles down on your LiPo (lithium polymer) cells / battery, but not plugged in all the time. When not being used for several hours, turn it off.
And best "tip" is if its near a socket,...plug it in as long as you can (especially at home) since cycle count on the battery are the "miles that wear out the tires (battery)", however again, not plugged in all or most of the time.
General rule to remember of Lithium batteries is:
Never drain them LOW & dont always/often store them HIGH
While cycle count is commonly seen to be the “miles” on your Lithium Ion pack cell in your Macbook, which they are, this distinction is not a fine line at all, and it is a big misconception to “count charge cycles”
*A person who has, for example, 300 charge cycles on their battery and is recharging at say 50-60% remaining of a 100% charge has better battery usage and care than another person who has 300 charge cycles at say 15% remaining on a 100% charge.
DoD (depth of discharge) is far more important on the wear and tear on your Macbook battery than any mere charge cycle count. *There is no set “mile” or wear from a charge cycle in general OR in specific.    As such, contrary to popular conception, counting cycles is not conclusive whatsoever, rather the amount of deep DoD on an averaged scale of its use and charging conditions.
                          (as a very rough analogy would be 20,000 hard miles put on a car vs. 80,000 good miles being something similar)
*Contrary to some myths out there, there is protection circuitry in your Macbook and therefore you cannot overcharge it when plugged in and already fully charged
LiPo (lithium polymer, same as in your Macbook) batteries do not need conditioning. However...
A lot of battery experts call the use of Lithium cells the "80% Rule" ...meaning use 80% of the charge or so, then recharge them for longer overall life.
Never let your Macbook go into shutdown and safe mode from loss of power, you can corrupt files that way, and the batteries do not like it.
The only quantified abuse seen to Lithium cells are instances when often the cells are repeatedly drained very low…. key word being "often"
Contrary to what some might say, Lithium batteries have an "ideal" break in period. First ten cycles or so, don't discharge down past 40% of the battery's capacity. Same way you don’t take a new car out and speed and rev the engine hard first 100 or so miles.
Proper treatment is still important. Just because LiPo batteries don’t need conditioning in general, does NOT mean they dont have an ideal use / recharge environment. Anything can be abused even if it doesn’t need conditioning.
From Apple on batteries:
http://support.apple.com/kb/HT1446
http://www.apple.com/batteries/
Storing your MacBook
If you are going to store your MacBook away for an extended period of time, keep it in a cool location (room temperature roughly 22° C or about 72° F). Make certain you have at least a 50% charge on the internal battery of your Macbook if you plan on storing it away for a few months; recharge your battery to 50% or so every six months roughly if being stored away. If you live in a humid environment, keep your Macbook stored in its zippered case to prevent infiltration of humidity on the internals of your Macbook which could lead to corrosion.
Considerations:
Your battery is subject to chemical aging even if not in use. A Lithium battery is aging as soon as its made, regardless.
In a perfect (although impractical) situation, your lithium battery is best idealized swinging back and forth between 20 and 85% SOC (state of charge) roughly.
Further still how you discharge the battery is far more important than how it is either charged or stored short term, and more important long term that cycle counts.
Ultimately counting charge cycles is of little importance. Abuse in discharging (foremost), charging, and storing the battery and how it affects battery chemistry is important and not the ‘odometer’ reading, or cycle counts on the battery.
Everything boils down to battery chemistry long term, and not an arbitrary number, or cycle count.
Keep your macbook plugged in when near a socket since in the near end of long-term life, this is beneficial to the battery.
Peace
Battery calibration, battery memory, battery overcharging, battery training, …all these concepts are mostly holdovers from much older battery technology, and on older Apple portable Macbooks ranging from early nicads, NiMh and otherwise; and these practices do not apply to your lithium battery and its smart controllers.
Calibrating the battery on older Apple portable Macbooks with removable batteries.
http://support.apple.com/kb/PH14087
There is no calibration of current Apple portable Macbooks with built-in batteries.
http://support.apple.com/ht1490
There is no battery calibration with current Apple portable Macbooks with built-in batteries. Lithium batteries have essentially a 0-‘memory’, and all such calibration involve the estimations fed to the system controller on the SOC (state of charge) of the battery over long periods of time as the battery degrades. The software based battery controller knows the battery's characteristics, or SOC and adjusts itself. This is why there is both no need and purpose to periodically deeply drain your macbook battery, since it doesn’t affect the characteristics of the battery, and further still deep discharges are something you should not do on purpose to any lithium battery.

External hard drive taking really long time to reformat

I'm reformatting a Seagate 2TB external hard drive that connects using USB 3.0 to my 2014 Macbook Pro (OS X 10.9.4).
For some idiotic reason (because I had never used it before and wanted to see what happened), when I went to reformat the drive in Disk Utility from FAT32 into 'Mac OS Journaled (Extended)' I selected the option for "7 Pass Secure Erase". It initially told me it should take "1 day, 7 hours", which seemed like a lot but was consistent with what other Support Communities people have said for such a large drive.
It's now been reformatting for 20 hours, and the estimated time remaining says "1 day, 1 hour". The progress bar has moved and it says it's on pass #3, but this seems like it's taking an abnormally long time. Has something gone wrong? For reference, I did a 1-pass into reformat into FAT32 on a similar 1TB external and it only took me around 20 minutes (so I estimated the new one would take ~5 hours (20 * ~2X storage space, 7 passes). I know "estimated time" on a computer always defies the laws of mathematics, but if "6 hours" is actually 20 hours, will I really be waiting for another 80 hours? Can I do anything to speed this up?
More importantly, can I stop the reformat and try it a gain with 1-pass, now that I've initiated the idiot way of doing it? I don't want to screw the drive up or make it unreadable, it's brand new, but I don't want to have to leave my laptop on for the next 3 and a half days.
Please help! Thanks so much!

SquareWarren wrote:
I'm reformatting a Seagate 2TB external hard drive that connects using USB 3.0...
...I know "estimated time" on a computer always defies the laws of mathematics, but if "6 hours" is actually 20 hours, will I really be waiting for another 80 hours? Can I do anything to speed this up?...
I don't know which Seagate external you're using but my experience with a number of GoFlex externals has been that very little thought was given to ventilation, and, as a result, the drives tended to overheat. Watching the transfer rate using Activity Monitor during normal backup use, I found that after running a while and getting hot, the transfer rate went from MB's to KB's/sec. You're not actually transferring anything but the drive is being written to, so I'd expect the write speed to drop and what is already going to be a long process will just get longer. Sorry.

T400 boot time takes long time & has issue with restart

Not sure if any one has already posted this and got replies...
my T400 has a strange issue. it takes a lot time in pre-boot... a cursor blinks on the top left corner for 5+ minutes and then loads the 'Windows loading...' screen for about another 5 mins and finally shows the windows logon screen.
Additionaly, when i hit shutdown, i am fine. if i hit restart - i am sitting there for ever.
my laptop has 8GB RAM + 256 GB SSD + Windows 7 Ultimate x64.

Srini,
I brought your tweet in and started a new thread and then found you already had a forum discussion going, so I'll just apend to your original thread and will leave this since I tweeted the link back to you to let you know we were taking a look.(Apologies)
Does this abnormally long startup of your T400 occur when docked or by itself? On battery or on AC power?
Have you checked the boot device order in BIOS? Make sure HDD is listed first.
Are there a lot of applications being loaded in the startup folder?
Have you tried using the MSCONFIG utility (start -> run ->msconfig) and then selected the startup tab to see what programs are being loaded during boot and if you can uncheck some that you don't always need to load?
This could reduce your boot time. I believe this, along with some setting tweaks was suggested in a similar T400 slow boot thread here...
Perhaps other members will have additional suggestions....
Mark
ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
Mark Hopkins
Program Manager, Lenovo Social Media (Services)
twitter @lenovoforums
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Inconsistency with maintenance cycle and task list phases in ChaRM

Hi Experts,
I'm deploying ChaRM with SolMan 4.0 SP09.
I was testing a scenario where there are more than one maintenance project open for same landscape (different logical components but values are the same). I have been using maintenance cycle document (in crmd_order) to control phase changes both in task list and in maintenance cycle.
I received an error message stating that the system has reset the status of the maintenance cycle and the end result was that task list phase is one step ahead of the maintenance cycle. This of course causes the situation where certain actions are no longer possible (maintenance cycle in Dev with release but task list already in test => release and import are not possible and reseting phase with task list is prevented by ChaRM).
My question is how do I restore the inconsistency. I have looked for notes (but of course this is not a notes issue) and the internet for solution.
I am very greatful for any hints you may give me!
Kind regards,
Auli

Thank you!
Exactly what I'm trying to do. I'll give it a go and get back to you asap.
BR
Auli

Downloading Mountain Lion ... taking too long.

Currently downloading Mountain Lion. However it is taking an abnormally long time. Not the internet provider ... suggestions?

Thank you for the feed back, appreciated. Will keep being patient. Others have reported it does take some time, but I was just becoming somewhat concerned as it has already been 2hrs and it doesn't even to have seemed to reach the half way point.
Will go with the provider theory

10.4.7 update -- how long for restart?

I just downloaded the subject update and it took a looooong time to restart. Is that normal? It appeared to have a lot of security elements and I was wondering if it was going through all my files. Previous restarts following updates have taken only a brief period of time.
I have recently installed VirusBarrier X4.
Dave
PowerBook G4 Mac OS X (10.4.7)

Long restarts directly prior to Mac OS X updates are to be expected.
From this article: http://www.macfixit.com/article.php?story=20060627132933535
"note that the first restart after applying Mac OS X 10.4.7 may be abnormally long. Subsequent restarts should take place at normal speed."

Abnormal long CMS GC cycles

Similar Messages

Maybe you are looking for