Time to compress greatly varies

I compressed a 1 1/2 project in Final Cut 5.1 using Compressor to mpg2 for DVD Studio Pro 4. The first time I compressed it took less than 1 1/2 hours. I re-edited the original to shorten it and compressed again and it is taking 5 hours. Can anyone tell me why there would be such a difference in the length to compress when all other settings are the same? Tanks

One more thing. I delete the copy of dtpad in my home directory and let it find the real one using the PATH. With HOME set to the local directory it took 0.527s to find it. With HOME set to the remote directory it took 2.139s. Same PATH in both cases. So how does $HOME fit into the $PATH search ?

Similar Messages

Does Time Machine Compress My Data?

Can I use a 160Gb external drive to back up more than 160Gb of data on my computer? Does Time Machine compress anything, or would I have to decide what to back up and what not to?

Time Machine doesn't compress anything. It is better to have a destination Time Machine hard drive that is twice the capacity of the source. Compression can lead to data corruption, or unrecoverability because the data compression engine may not have a compatible decompressor at the time of recovery.

Every time I compress a file over 1.5 Gigs it ends up corrupt any idea what the cause is?

Every time I compress a file over 1.5 Gigs it ends up corrupt any idea what the cause is?

Compression depends on repetativeness of characters within the file. If it can't map those, it won't compress. Images and programs are much harder to compress for that reason, as they both are basically binary constructs. Some image software compresses looking at common lines and points of the same color. Audio files look for the same frequency. Most video formats are already compressed to some extent except full DV.
And files with DRM get even more dicy, since you really can't bypass the DRM which itself is binary code, not to mention not allowed to be copied. This forum can't discuss such issues due to the DMCA rules. As long as it isn't copyright, what are you trying to compress?

My iPhone 4 home button doesn't always work. sometimes its just not responsive. other times, it works great. what's the problem, and how do I get it fixed? my iphone is 2 days old

my iPhone 4 home button doesn't always work. sometimes its just not responsive. other times, it works great. what's the problem, and how do I get it fixed? my iphone is 2 days old

Hi there,
I would recommend taking a look at the troubleshooting steps found in the article below.
iPhone: Hardware troubleshooting
http://support.apple.com/kb/TS2802
-Griff W.

HT201250 Does time machine compress the data in backup?

I have got to replace my internal hard drive so have to back up just everything to an ext drive.
When I use 'time machine' to back up to an external disk, does that disk have to be larger than the file size on my iMac?
Does Time machine compress the data?( eg will 1TB fit on a 500 gig external drive?)
Thanks

No, Time Machine doesn't compress the data. I recently started a new TIme Machine backup, and the first backup required the same amount of space as it was backing up (actually a little bit more during the backup process).

Time/Pitch Compression/Expansion - Dirac Le

hi guys, just wanted to point some attention to some great software that is available freely to any manufacturer that creates sequencers. it's time/pitch expansion/compression software and it's called Dirac...for a respectable price there's a full blown version too that offers amazing features.
let's hope that apple include this in their next release of logic pro; whenever that will be i don't know.
check it out and let's hope that Apple see this!
http://www.bernsee.com/dspdimension.com/index.html?dirac.html

It would be great to have it natively in FCP to alleviate the need to export/import which is time consuming.
By the way, it has been months at this point, but it was great to meet you Shane at NAB earlier this year in the Matrox booth. We spoke about the MXO2, which I am ordering next week. I need a solution for DVCProHD 720p24 up-conversion to HDCAM 1080i 29.97, and the MXO2 seems like a good reasonably price solution for that. My MXO has been a solid output for color correction on my 23" ACD. Much nicer than my Sony 1354q.

FileUpload using JAX-WS webservice on weblogic 10.3.5 is taking long time for files greater than 10MB

I am trying to upload a file using JAX-WS webservice which is deployed on the weblogic 10.3.5 server.Even before the code reaches the Service Endpoint lot of time is being spent at the weblogic layer. for files less than 10MB the performance is good but for files greater than 10 MB it takes around 3 mins to complete the request. I did take thread dumps and I see the thread servicing the requests is taking lot of time when executing SAX2DOMEx.characters it consumes around 80 -85 % of time here. Is there anything that I can do to improve the performance here ?
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=37 idx=0x90 tid=16848 prio=5 alive, suspended, native_blocked, daemon
                at jrockit/vm/Allocator.allocLargeObjectOrArray(JIZ)Ljava/lang/Object;(Native Method)
                at jrockit/vm/Allocator.allocObjectOrArray(Allocator.java:349)[optimized]
                at jrockit/vm/StringMaker.toString(StringMaker.java:188)[inlined]
                at com/sun/org/apache/xerces/internal/dom/CharacterDataImpl.appendData(CharacterDataImpl.java:191)[optimized]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:218)[inlined]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:209)[optimized]
                at com/sun/xml/ws/message/SAX2DOMWriterEx.writeCharacters( .java:108)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.handleCharacters(XMLStreamReaderToXMLStreamWriter.java:153)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.bridge(XMLStreamReaderToXMLStreamWriter.java:114)
                at com/sun/xml/ws/message/stream/StreamMessage.writePayloadTo(StreamMessage.java:313)
                at com/sun/xml/ws/message/stream/StreamMessage.writeEnvelope(StreamMessage.java:343)
                at com/sun/xml/ws/message/stream/StreamMessage.writeTo(StreamMessage.java:321)
                at com/sun/xml/ws/message/AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:226)
                at com/sun/xml/ws/handler/SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:87)
                at weblogic/wsee/jaxws/framework/jaxrpc/SOAPMessageContext.getMessage(SOAPMessageContext.java:252)
                at weblogic/wsee/security/wssp/handlers/WssHandler.getSecurityContext(WssHandler.java:318)
                at weblogic/wsee/security/wssp/handlers/WssHandler.preValidate(WssHandler.java:420)
                at weblogic/wsee/security/wssp/handlers/PreWssServerPolicyHandler.processRequest(PreWssServerPolicyHandler.java:25)
                at weblogic/wsee/security/wssp/handlers/WssHandler.handleRequest(WssHandler.java:112)
                at weblogic/wsee/jaxws/framework/jaxrpc/TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
                at com/sun/xml/ws/api/pipe/Fiber.__doRun(Fiber.java:866)
                at com/sun/xml/ws/api/pipe/Fiber._doRun(Fiber.java:815)
                at com/sun/xml/ws/api/pipe/Fiber.doRun(Fiber.java:778)
                at com/sun/xml/ws/api/pipe/Fiber.runSync(Fiber.java:680)
                ^-- Holding lock: com/sun/xml/ws/api/pipe/Fiber@0x83736a70[biased lock]
                at com/sun/xml/ws/server/WSEndpointImpl$2.process(WSEndpointImpl.java:403)
                at com/sun/xml/ws/transport/http/HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
                at com/sun/xml/ws/transport/http/HttpAdapter.handle(HttpAdapter.java:253)
                at com/sun/xml/ws/transport/http/servlet/ServletAdapter.handle(ServletAdapter.java:140)
                at weblogic/wsee/jaxws/WLSServletAdapter.handle(WLSServletAdapter.java:171)
                at weblogic/wsee/jaxws/HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:146)
                at weblogic/wsee/util/ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
                at weblogic/wsee/jaxws/HttpServletAdapter$3.run(HttpServletAdapter.java:311)
                at weblogic/wsee/jaxws/HttpServletAdapter.post(HttpServletAdapter.java:336)
                at weblogic/wsee/jaxws/VerboseHttpProcessor.post(VerboseHttpProcessor.java:39)
                at weblogic/wsee/jaxws/JAXWSServlet.doRequest(JAXWSServlet.java:98)
                at weblogic/servlet/http/AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
                at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
                at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
                at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:300)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:183)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.wrapRun(Lweblogic/servlet/internal/ServletStubImpl;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Ljava/lang/Object;(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(Unknown Source)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:120)
                at weblogic/servlet/internal/WebAppServletContext.securedExecute(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Z)V(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext.execute(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V(Unknown Source)
                at weblogic/servlet/internal/ServletRequestImpl.run()V(Unknown Source)
                at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209)
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

I am trying to upload a file using JAX-WS webservice which is deployed on the weblogic 10.3.5 server.Even before the code reaches the Service Endpoint lot of time is being spent at the weblogic layer. for files less than 10MB the performance is good but for files greater than 10 MB it takes around 3 mins to complete the request. I did take thread dumps and I see the thread servicing the requests is taking lot of time when executing SAX2DOMEx.characters it consumes around 80 -85 % of time here. Is there anything that I can do to improve the performance here ?
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=37 idx=0x90 tid=16848 prio=5 alive, suspended, native_blocked, daemon
                at jrockit/vm/Allocator.allocLargeObjectOrArray(JIZ)Ljava/lang/Object;(Native Method)
                at jrockit/vm/Allocator.allocObjectOrArray(Allocator.java:349)[optimized]
                at jrockit/vm/StringMaker.toString(StringMaker.java:188)[inlined]
                at com/sun/org/apache/xerces/internal/dom/CharacterDataImpl.appendData(CharacterDataImpl.java:191)[optimized]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:218)[inlined]
                at com/sun/xml/bind/marshaller/SAX2DOMEx.characters(SAX2DOMEx.java:209)[optimized]
                at com/sun/xml/ws/message/SAX2DOMWriterEx.writeCharacters( .java:108)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.handleCharacters(XMLStreamReaderToXMLStreamWriter.java:153)
                at com/sun/xml/ws/util/xml/XMLStreamReaderToXMLStreamWriter.bridge(XMLStreamReaderToXMLStreamWriter.java:114)
                at com/sun/xml/ws/message/stream/StreamMessage.writePayloadTo(StreamMessage.java:313)
                at com/sun/xml/ws/message/stream/StreamMessage.writeEnvelope(StreamMessage.java:343)
                at com/sun/xml/ws/message/stream/StreamMessage.writeTo(StreamMessage.java:321)
                at com/sun/xml/ws/message/AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:226)
                at com/sun/xml/ws/handler/SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:87)
                at weblogic/wsee/jaxws/framework/jaxrpc/SOAPMessageContext.getMessage(SOAPMessageContext.java:252)
                at weblogic/wsee/security/wssp/handlers/WssHandler.getSecurityContext(WssHandler.java:318)
                at weblogic/wsee/security/wssp/handlers/WssHandler.preValidate(WssHandler.java:420)
                at weblogic/wsee/security/wssp/handlers/PreWssServerPolicyHandler.processRequest(PreWssServerPolicyHandler.java:25)
                at weblogic/wsee/security/wssp/handlers/WssHandler.handleRequest(WssHandler.java:112)
                at weblogic/wsee/jaxws/framework/jaxrpc/TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
                at com/sun/xml/ws/api/pipe/Fiber.__doRun(Fiber.java:866)
                at com/sun/xml/ws/api/pipe/Fiber._doRun(Fiber.java:815)
                at com/sun/xml/ws/api/pipe/Fiber.doRun(Fiber.java:778)
                at com/sun/xml/ws/api/pipe/Fiber.runSync(Fiber.java:680)
                ^-- Holding lock: com/sun/xml/ws/api/pipe/Fiber@0x83736a70[biased lock]
                at com/sun/xml/ws/server/WSEndpointImpl$2.process(WSEndpointImpl.java:403)
                at com/sun/xml/ws/transport/http/HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
                at com/sun/xml/ws/transport/http/HttpAdapter.handle(HttpAdapter.java:253)
                at com/sun/xml/ws/transport/http/servlet/ServletAdapter.handle(ServletAdapter.java:140)
                at weblogic/wsee/jaxws/WLSServletAdapter.handle(WLSServletAdapter.java:171)
                at weblogic/wsee/jaxws/HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:146)
                at weblogic/wsee/util/ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
                at weblogic/wsee/jaxws/HttpServletAdapter$3.run(HttpServletAdapter.java:311)
                at weblogic/wsee/jaxws/HttpServletAdapter.post(HttpServletAdapter.java:336)
                at weblogic/wsee/jaxws/VerboseHttpProcessor.post(VerboseHttpProcessor.java:39)
                at weblogic/wsee/jaxws/JAXWSServlet.doRequest(JAXWSServlet.java:98)
                at weblogic/servlet/http/AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
                at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
                at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
                at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:300)
                at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:183)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.wrapRun(Lweblogic/servlet/internal/ServletStubImpl;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Ljava/lang/Object;(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(Unknown Source)
                at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
                at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:120)
                at weblogic/servlet/internal/WebAppServletContext.securedExecute(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Z)V(Unknown Source)
                at weblogic/servlet/internal/WebAppServletContext.execute(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V(Unknown Source)
                at weblogic/servlet/internal/ServletRequestImpl.run()V(Unknown Source)
                at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209)
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

ICal doesn't show delegation, and generates date and time error messages in /var/log/system.log

I have a problem with my iCal, when I use my caldav account, I can only see my own calendar on my MBA, on my co-workers MBP it works fine with both my account and his. My co-worker can't see other calendars than his own when he uses iCal on my laptop.
We can reproduce this problem on his computer by setting Location to Automatic rather than Amsterdam, then after deleting iCal's cache files, the caldav account and setting the Location back to Amsterdam solves the problem for him.
It does not solve the problem for me (or several other co-workers). We've been looking at this for a few weeks, and we can not find any clear pattern why certain machines have this problem and others don't.
All machines (both affected and unaffected) are running Mac OS 10.7.2 with iCal 5.0.1
I've spoken to Apple support over the phone (in the Netherlands), unfortunately, they couldn't help with this.
So far we've tried numerous location and language settings, but on affected machines nothing appears to solve the delegation problem (which we assume to be connected to the error messages iCal generates)
Starting iCal yeilds the following error messages in /var/log/system.log:
Jan 5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
Jan 5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=3
          line 1,6: unexpected char: '='
Jan 5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
Jan 5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=10
          line 1,6: unexpected char: '='
Jan 5 11:31:05 dhcp-91 iCal[23884]: Unexpected EOF, returning last token as fallback
Jan 5 11:31:05 dhcp-91 iCal[23884]: VTIMEZONE does not match System Time Zone (Europe/Amsterdam) for 20100105T000000 to 20120105T000000: (
              "interval: 2001-01-01 01:00:00 +0100, offset: 3600"
          ) != (
              "interval: 2010-03-28 03:00:00 +0200, offset: 7200",
              "interval: 2010-10-31 02:00:00 +0100, offset: 3600",
              "interval: 2011-03-27 03:00:00 +0200, offset: 7200",
              "interval: 2011-10-30 02:00:00 +0100, offset: 3600"
          BEGIN:VTIMEZONE
          X-LIC-LOCATION:Europe/Amsterdam
          TZID:Europe/Amsterdam
          BEGIN:DAYLIGHT
          TZOFFSETFROM:+0100
          TZNAME:CEST
          TZOFFSETTO:+0200
          DTSTART:19700329T020000
          END:DAYLIGHT
          BEGIN:STANDARD
          TZOFFSETFROM:+0200
          TZNAME:CET
          TZOFFSETTO:+0100
          DTSTART:19701025T030000
          END:STANDARD
          END:VTIMEZONE
Jan 5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
Jan 5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=3
          line 1,6: unexpected char: '='
Jan 5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
Jan 5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=10
          line 1,6: unexpected char: '='
Jan 5 11:31:05 dhcp-91 iCal[23884]: Unexpected EOF, returning last token as fallback
Jan 5 11:31:05 dhcp-91 iCal[23884]: VTIMEZONE does not match System Time Zone (Europe/Amsterdam) for 20100105T000000 to 20120105T000000: (
              "interval: 2001-01-01 01:00:00 +0100, offset: 3600"
          ) != (
              "interval: 2010-03-28 03:00:00 +0200, offset: 7200",
              "interval: 2010-10-31 02:00:00 +0100, offset: 3600",
              "interval: 2011-03-27 03:00:00 +0200, offset: 7200",
    "interval: 2011-10-30 02:00:00 +0100, offset: 3600"
          BEGIN:VTIMEZONE
          X-LIC-LOCATION:Europe/Amsterdam
          TZID:Europe/Amsterdam
          BEGIN:DAYLIGHT
          TZOFFSETFROM:+0100
          TZNAME:CEST
          TZOFFSETTO:+0200
          DTSTART:19700329T020000
          END:DAYLIGHT
          BEGIN:STANDARD
          TZOFFSETFROM:+0200
          TZNAME:CET
          TZOFFSETTO:+0100
          DTSTART:19701025T030000
          END:STANDARD
          END:VTIMEZONE
And when I close iCal I get:
Jan 5 11:33:25 dhcp-91 [0x0-0x592592].com.apple.iCal[23894]: token mismatch: 4 != 5

I'm seeing the same thing, and I can't even find where OS X stores calendars on disk anymore...

Total of %db time column is greater than 100 in AWR report

Hello,
I have a query regarding "To 5 timed foreground events" section of AWR report.
On many occassions I found that the sum of all the values in the %db time column as mentioned above is grater than 100.
How can percentage be greater than 100?
Event
Waits
Time(s)
Avg wait (ms)
% DB time
Wait Class
DB CPU
29,212
98.18
latch: shared pool
2,291
286
125
0.96
Concurrency
direct path read
147,998
112
1
0.38
User I/O
library cache: mutex X
4,831
92
19
0.31
Concurrency
log file sync
36,736
72
2
0.24
Commit
In the above case the total comes up to just 100.07 % but I have seen reports where the total goes beyond 120 % -130 %.
Can you explain why this happens, please?
Thanks,
Rushi

Can someone explain above situation, please?

Time machine compression ratio

I know that previously Time Machine didn't do any compression, it is 1:1, but it seems that even on Mavericks it still doesn't.
How is it possible that with all Apple inovation they still didn't come up with the way to compress the image.
Why do I need to back up almost 1Tb of Data equally to 1Tb data where is the logic in it?
I haven't found a way or options to see if there is a way to compress the image, but Time Machine options are pretty basic and I couldn't find anything to work with.
Anyone had better luck or we are all in the same boat here?

If you have 700GB of data then obviously you need at least 700GB of space to do one full backup. Beyond that the amount of space needed will be dictated by how much changes and how often. Time Machine makes and keeps backups according to the following default schedule
Hourly backups for the last 24 hours the Mac has been turned on, if it has been on continuously for the last 24 hours that will be 24 backups
Daily backups for the last month, it is has been on each day for the last month that will be about 30 backups depending on which month
Weekly backups for as many weeks as the Mac has been running and doing backups, until the backup drive is full, if you have enough space for a year that would be 52 backups
See http://support.apple.com/kb/ht1427
So as a hypothetical total number of backups for one year and assuming the Mac was on every day for that year and there was enough space this would total something like -
24 + (number of days in month) + (number of weeks in a year) = 106
It might actually be a bit less because I am not sure if it keeps daily and weekly backups for the latest/current month, if it does not it might be more like 101.
Now if on average 10% of files change per day then we would need for an entire years backups the following amount
1 x 700GB + (365 x (700GB x 10%)) = 26250GB
In reality you may have far less than 10% change per day, as a comparison lets use 1% changing per day
1 x 700GB + (365 x (700GB x 1%)) = 3255GB
As a minimum Time Machine will try and keep backups for the last day and last month which would be 24 + 30 backups, it then keeps as many weekly backups as will fit. Once it runs out of space it is supposed to automatically throw away the older backups. So if we start from new we have the following numbers of backups (assuming it is running all day everyday and have enough space)
End of day 1 = 24 backups
End of day 2 = 24 + 1 = 25 backups
End of month 1 = 24 + 30 = 54 backups
End of month 2 = 24 + 30 + 1 = 55 backups
End of month 3 = 24 + 30 + 4 = 59 backups
End of month 4 = 24 + 30 + 8 = 63 backups
End of month 12 = 24 + 30 + 52 = 106 backups
As far as I can see Time Machine really wants to keep a minimum of an entire day i.e. 24 backups plus an entire month i.e. 30 = 54 backups plus a weekly backup, if you don't have enough space for that i.e. 55 backups then I suspect it will get upset and complain about space regardless of its supposed ability to automatically throw away older backups.
Going back to our space formula, if we estimate a change rate of 1% per day this means I feel Time Machine would need a minimum space of
1 x 700GB + ((1 + 30 + 7) x (700GB x 1%)) = 966GB
However I think it wise to assume it would be happier with a bit more than that for working space etc.
Note: the above reflects one day plus one month (i.e. 30 days) plus one weekly backup i.e. a total of 32 backups, or more importantly the equivalent of 38 days of changes. As we are estimating a daily change rate of 1% the fact there are 24 backups for the latest day makes no difference to the amount changed, you are not changing 1% per hour, but 1% per day, the changes would be merely split in to 24 hourly backups.
This should give you a way of more accurately judging how big a backup drive you need.
If you are finding it is not throwing stuff away then maybe you don't have enough space for the (I feel) minimum of 1 day + 1 month + 1 week, however I also feel as per the following article that sometimes Time Machine just gets confused and unable to throw away older backups. See -
http://www.macworld.co.uk/news/mac/time-machine-says-drive-full-what-should-i-do -3456272/

Time Machine compression ratio or 1:1?

I remember reading (or imagined I remember reading) that Time Machine uses some compression when backing up so that, if you're backing up 50Gb, it's not literally 50Gb backup file. I am referring to the initial backup of course. Incremental backups may add file size too, I'm aware. I'm also wondering if there is compression, how you can figure out what size drive to use for all backups, if you don't have a Time Capsule. If I have say, 5 drives totally 1Tb, do I need another 1Tb drive as my backup destination?

Time machine does not use any compression whatsoever. it's straight 1-1 copy.
as for the size of the backup drive, the general rule of thumb is that the backup drive should be at least two times bigger than the total amount of data you are backing up. if you can not provide that, don't use TM for backups, use something else which does not store incremental backups.

Audition CS6 Time Expansion / Compression

I work in a broadcast environment (radio). We use Audition CS6 in all of our production studios. All output from Audition must be either MP3 with a sample rate of 44100 Hz, stereo 16-bit or WAV files. Promos and underwriting announcements are typically 30-second and occasionally 60-seconds in length. Other segments range from a few minutes to a max of 58 minutes. What ever the length, it must be exact. For example a half hour segment targeted to run for 29:00.000 may end up 28:57.043 or 29:03.495. How can do I expand or compress the time of a session without altering the pitch? Sessions may be either single mono tracks or multichannel stereo tracks. This has become an urgent situation for us due to the installation of a new automation system that requires exact times and does not provide this time squeeze/expand feature.

Should be straightforward. Effects>Time and Pitch> Stretch and Pitch (process).
Use Radius, and simply put in the new duration on the RHS - no sums involved!
Set the precision to High, and make sure that there isn't a check in the pitch shift box - so the pitch shift always stays at 0 semitones. Then, all you will get is a stretch (or shrink if you over-run). You may also want or need to play with the options in the Advanced settings as well, but that's the basics of it.
Or just look at the answer in your other thread that I've just noticed...

Query is taking longer exeuction time after compressing the cube

Hi,
we have compresed 15cubes at once using process chain. After Infocube compression, queries present on top of these cubes taking longer execution times at statement CL_SQL_RESULT_SET=============CP.
Please let us know how to deal with this query performance.
Thanks,
Navis

try to run the query in RSRT in execute and debug mode..
see this http://forums.sdn.sap.com/thread.jspa?threadID=1713040
http://forums.sdn.sap.com/thread.jspa?threadID=1541660

ServerStats problem. "Database Time Per Sec" greater than 100 centisecs

Hi,
I have set up a ServerStat to read the V$SYSMETRIC table.
OLT reports the value to be greater than 100 centisecs.
How is this possible?
Regards,
Axel
Edited by: ao on 2011-feb-22 13:17

As Kecskemethy points out, the CPU count matters but so does the number of active sessions.
Imagine a simple example where you have a single CPU core and you have 100 sessions. Session 1 does a SELECT ... FOR UPDATE on a single row in a table. Session 1 then does some work that requires 1 second of CPU time and does no I/O. Sessions 2-99 do a SELECT ... FOR UPDATE on that same single row just after session 1 gets the lock. The total database time that Oracle will count for that single second is 100. Session 1 will have 1 second of database time due to CPU. Sessions 2-99 will each have 1 second of database time due to lock contention.
If you're looking at generalized performance, total database time is often a superior metric to something like CPU time because it's measuring all the waits that all your users are actually experiencing. If session 1 is idle (doing no work) while it is holding the lock (say, because it is waiting on a user to press a button in the GUI), the CPU and I/O utilization of the server may be minimal but you may have dozens or hundreds of users racking up significant wait time.
Justin

Project time became compressed

Something happened to my project and it now speeds through my pictures in a fraction of the original time. Originally each picture was set to 6 seconds, but now each one shows in under 1 second and they look like they became compressed in the storyboard area. Any idea how to fix this, and/or what caused it?
Thanks!

Sometimes permissions and preferences can get corrupted. Whenever iMovie starts acting funny, a common maintenance procedure is to do the following: Delete preferences by closing iMovie and trashing the file com.apple.iMovie.plist found in User (the House icon)/Library/Preferences. Then do a permissions repair using the Utilities/Disk Utility App on your Mac. Open the Disk Utilities window and select the Mac hard drive icon at the top of the side pane at the left. Then click on the Repair Permissions button. When you have repaired permissions and deleted preferences, restart your computer and launch iMovie. iMovie will replace the .plist file that you deleted. Be sure also that you have sufficient free disk space on your hard drive for iMovie to function correctly. 25GB often is recommended by users of this forum. After doing all of the above, relaunch iMovie and see whether you still have the problem.
If that doesn't work you will need to remove the transitions and reset the durations of the photo clips. (*As always, be sure to make a back up copy of your project before making any changes.*)
To remove transitions and reset durations:
+Select one transition in your string of clips.+
+Edit > Select Similar Clips. (All of the transition clips will now be selected, but not the photo clips.)+
+Delete (this will remove all of the transitions. If you don't like the result, Edit > Undo and delete them manually.)+
+Select a string of contiguous photos whose durations you want to change.+
+Media > Show Photo Settngs+
+Reset the durations to 6 seconds in the Show Photo Settings box.+
If you haven't saved your project since this glitch manifested, and are confident that you know what you are doing, another way might be to Control click on the project icon and then hit Show Package Contents. (Make sure you have backed up your project first.) There should be a file in there named Project Name~.iMovieProject. That is your last saved version of the project. Open that file and see if your project is displayed in there intact as it was before the glitch manifested. If it is, you can copy (not remove) it and move the copy to a new iMovie project and be back where you were before the glitch. *But be careful not to make any changes, remove, or rename any of the files in the Package Contents, or you will make your original project nonfunctional*. So do this at your own risk.

Time to compress greatly varies

Similar Messages

Maybe you are looking for