64-bit's biggest advantage is allowing you to drastically increase your memory address space so if you have enough Ram, you can use all of it for any given process. Photos are good because they give you clear visual feedback about what's going on so they're good for a demonstration.
SJ wouldn't be prodding Adobe to make PS 64 bit would he? He wouldn't do anything like that.
64-bit's biggest advantage is allowing you to drastically increase your memory address space so if you have enough Ram, you can use all of it for any given process. Photos are good because they give you clear visual feedback about what's going on so they're good for a demonstration.
On x86, going 64 bit, runs most programs faster. This is unlike the PPC platform, where 64 bit runs programs no faster, or sometimes, even slightly slower.
On x86, going 64 bit, runs most programs faster. This is unlike the PPC platform, where 64 bit runs programs no faster, or sometimes, even slightly slower.
Not sure where Melgross got the "slightly slower on PPC" thing from, but on the x86 front: if the programs are specially compiled for 64 bit, they have the potential to execute faster (even if they don't need any fixed-point 64 bit maths) because 64 bit x86 has twice as many registers as x86 32 bit.
Not sure where Melgross got the "slightly slower on PPC" thing from, but on the x86 front: if the programs are specially compiled for 64 bit, they have the potential to execute faster (even if they don't need any fixed-point 64 bit maths) because 64 bit x86 has twice as many registers as x86 32 bit.
On PowerPC 64bit you don't get the increase in registers so no increase there. The decrease comes from having to operate with 64bit data instead of 32bit so you've essentially halved the amount of data you can hold in the cache and you're operating with 64bit pointers for no reason.
On PowerPC 64bit you don't get the increase in registers so no increase there. The decrease comes from having to operate with 64bit data instead of 32bit so you've essentially halved the amount of data you can hold in the cache and you're operating with 64bit pointers for no reason.
So you are both saying that being 64bit itself doesn't make these chips faster, but the design of the chip is faster (due to increase in registers).
I assume then that those registers are only available when accessed via 64 bit instructions?
(I've just always read that 64bit is slightly slower - except on exceptionally large data files. Of course, if our general memory requirements double every year or 2, then we NEED 64 bit or we'd be forced shortly to install less memory than optimum and hence run more slowly on 32bit.)
So you are both saying that being 64bit itself doesn't make these chips faster, but the design of the chip is faster (due to increase in registers).
I assume then that those registers are only available when accessed via 64 bit instructions?
Yes.
The fastest operations are those which can be held in the CPU's registers. Think of them as extremely fast local storage on the CPU itself. The problem is the 32bit Intel platform only has 8 registers. 64bit Intel/AMD increases this to 16. PowerPC has always had 16 registers.
Compilers optimise code by using registers as much as they possibly can because they're really fast. The more they've got to play with, the more efficient the code generated. In theory, if the code can use only registers then the need to get data from the system memory is avoided and you get a massive increase in speed. In reality though, most of the register issues can be solved by clever compiler tricks and larger on chip caches at the expense of power consumption and rarely are computer algorithms just acting on small sets of data in registers and not accessing system RAM.
I just feel left out for not posting in this thread. I say the mini stays! Come Jan 2008 it will get an upgrade and Gates will let Steve announce to the world that he is finally getting that sex change !
I want features in iTunes and iPhoto that allow me to seamlessly break my library in to multiple locations. ie. Have a core of music on my laptop, have a mush larger family library on a shared machine and be able to sync them both seamlessly to my iPod. This is doable now with some behind the scenes file sharing but Apple could do a much better job if they set their minds to the challenge.
Hear hear, an Apple central media server. That would rule absolutely.
I still want a Mac Mini, I have since they were introduced. The more I think about how useful it would be sat under my TV as a server/media player, the more I salivate at the idea. And hopefully with these rumours regarding a Mac Nano, well, you just never know.
I think the 'mini is a cute machine. But I won't buy one - due to it being a bit under powered. On the other hand, I won't buy a Mac tower due to it's size and noise factor. I had a MDD dual 1Ghz G4 tower and it was loud as everything. I have heard that the newer machines are quieter, but I want whisper quiet. I have a iMac 24" now and it's perfect.
What about a Mac-midi that has a full-size (replaceable) hard drive and has the speed capability of a iMac. Basically a headless iMac. If something like this were in the $1000 range or so, I WOULD be interested.
The Mac Mini got a reprieve and a Core Duo option which is great. I still believe that the Mini is a great central server for many families. After all the AppleTV is basically a mains-powered iPod with a hi def video interface. To get the most out of the AppleTV you want a media server and the mini with an add-on disk does a great job.
Now what I am waiting for is for Leopard to provide an iTunes update that allows me to partition my music library. I want a subset on my laptop and the rest shared on a home media server so all my family can share our music.
Sorry if this has already been discussed but this thread is really long and I didn't read it all.
Does anyone have any advice on using the mini with Leopard server. Is the max ram really 2 gigs? can one disable the video shared ram? Is firewire 400 fast enough for external storage? Etc.
Does anyone have any advice on using the mini with Leopard server. Is the max ram really 2 gigs? can one disable the video shared ram? Is firewire 400 fast enough for external storage? Etc.
The latest mini will run with 3GB. OWC sells a 3GB kit for it. link
FW 400 is plenty fast enough for everyday stuff and server storage, in my opinion. For large transfers and high end video work, FW 800 or SATA is better.
The latest mini will run with 3GB. OWC sells a 3GB kit for it. link
FW 400 is plenty fast enough for everyday stuff and server storage, in my opinion. For large transfers and high end video work, FW 800 or SATA is better.
On my mini and iMac 24", I can never really tell that big of a mind blowing difference in moving large quantities of files. I thought FW800 would be 2x speed but I don't believe it is. So I think FW 400 would be fine for external storage since it works great with my Final Cut Studio setup.
On my mini and iMac 24", I can never really tell that big of a mind blowing difference in moving large quantities of files. I thought FW800 would be 2x speed but I don't believe it is. So I think FW 400 would be fine for external storage since it works great with my Final Cut Studio setup.
It depends on the device you are writing to. A single hard drive will usually have a maximum transfer rate of 75-100MBps which is 600-800Mbps. FW800 is 800Mbps so can work with the fastest rate the drive can take.
If your drive only reaches 40MBps = 320Mbps then you're not going to see much difference between FW400 and FW800. If on the other hand you target an external RAID setup where transfer rates are 150MBps (1200Mbps) and above, that's where FW800 and eSATA are needed.
If the mini is being used as a server, aren't you also limited by the transfer speed of your wired or wireless network? I'd think that would be the limiting factor, not the FW400 external drive.
If the mini is being used as a server, aren't you also limited by the transfer speed of your wired or wireless network? I'd think that would be the limiting factor, not the FW400 external drive.
Thanks for the replies.
Could be a non-issue, not sure if database queries are affected more so than other types of disk access. I just want to experiment so I suppose the limitations of the mini would be acceptable until such time as we decide to go live with iCal service. The plan is to migrate to xserve eventually.
Comments
64-bit's biggest advantage is allowing you to drastically increase your memory address space so if you have enough Ram, you can use all of it for any given process. Photos are good because they give you clear visual feedback about what's going on so they're good for a demonstration.
SJ wouldn't be prodding Adobe to make PS 64 bit would he? He wouldn't do anything like that.
64-bit's biggest advantage is allowing you to drastically increase your memory address space so if you have enough Ram, you can use all of it for any given process. Photos are good because they give you clear visual feedback about what's going on so they're good for a demonstration.
On x86, going 64 bit, runs most programs faster. This is unlike the PPC platform, where 64 bit runs programs no faster, or sometimes, even slightly slower.
On x86, going 64 bit, runs most programs faster. This is unlike the PPC platform, where 64 bit runs programs no faster, or sometimes, even slightly slower.
What makes you think this?
What makes you think this?
Not sure where Melgross got the "slightly slower on PPC" thing from, but on the x86 front: if the programs are specially compiled for 64 bit, they have the potential to execute faster (even if they don't need any fixed-point 64 bit maths) because 64 bit x86 has twice as many registers as x86 32 bit.
Not sure where Melgross got the "slightly slower on PPC" thing from, but on the x86 front: if the programs are specially compiled for 64 bit, they have the potential to execute faster (even if they don't need any fixed-point 64 bit maths) because 64 bit x86 has twice as many registers as x86 32 bit.
On PowerPC 64bit you don't get the increase in registers so no increase there. The decrease comes from having to operate with 64bit data instead of 32bit so you've essentially halved the amount of data you can hold in the cache and you're operating with 64bit pointers for no reason.
On PowerPC 64bit you don't get the increase in registers so no increase there. The decrease comes from having to operate with 64bit data instead of 32bit so you've essentially halved the amount of data you can hold in the cache and you're operating with 64bit pointers for no reason.
So you are both saying that being 64bit itself doesn't make these chips faster, but the design of the chip is faster (due to increase in registers).
I assume then that those registers are only available when accessed via 64 bit instructions?
(I've just always read that 64bit is slightly slower - except on exceptionally large data files. Of course, if our general memory requirements double every year or 2, then we NEED 64 bit or we'd be forced shortly to install less memory than optimum and hence run more slowly on 32bit.)
So you are both saying that being 64bit itself doesn't make these chips faster, but the design of the chip is faster (due to increase in registers).
I assume then that those registers are only available when accessed via 64 bit instructions?
Yes.
The fastest operations are those which can be held in the CPU's registers. Think of them as extremely fast local storage on the CPU itself. The problem is the 32bit Intel platform only has 8 registers. 64bit Intel/AMD increases this to 16. PowerPC has always had 16 registers.
Compilers optimise code by using registers as much as they possibly can because they're really fast. The more they've got to play with, the more efficient the code generated. In theory, if the code can use only registers then the need to get data from the system memory is avoided and you get a massive increase in speed. In reality though, most of the register issues can be solved by clever compiler tricks and larger on chip caches at the expense of power consumption and rarely are computer algorithms just acting on small sets of data in registers and not accessing system RAM.
I get back late, and don't even have to answer the question, because you guys did it for me.
BTW The mini ain't dead yet. :P
I want features in iTunes and iPhoto that allow me to seamlessly break my library in to multiple locations. ie. Have a core of music on my laptop, have a mush larger family library on a shared machine and be able to sync them both seamlessly to my iPod. This is doable now with some behind the scenes file sharing but Apple could do a much better job if they set their minds to the challenge.
Hear hear, an Apple central media server. That would rule absolutely.
I still want a Mac Mini, I have since they were introduced. The more I think about how useful it would be sat under my TV as a server/media player, the more I salivate at the idea. And hopefully with these rumours regarding a Mac Nano, well, you just never know.
Forget media speculation, long live the Mini!
I think the 'mini is a cute machine. But I won't buy one - due to it being a bit under powered. On the other hand, I won't buy a Mac tower due to it's size and noise factor. I had a MDD dual 1Ghz G4 tower and it was loud as everything. I have heard that the newer machines are quieter, but I want whisper quiet. I have a iMac 24" now and it's perfect.
What about a Mac-midi that has a full-size (replaceable) hard drive and has the speed capability of a iMac. Basically a headless iMac. If something like this were in the $1000 range or so, I WOULD be interested.
The Mac Mini got a reprieve and a Core Duo option which is great. I still believe that the Mini is a great central server for many families. After all the AppleTV is basically a mains-powered iPod with a hi def video interface. To get the most out of the AppleTV you want a media server and the mini with an add-on disk does a great job.
Now what I am waiting for is for Leopard to provide an iTunes update that allows me to partition my music library. I want a subset on my laptop and the rest shared on a home media server so all my family can share our music.
Does anyone have any advice on using the mini with Leopard server. Is the max ram really 2 gigs? can one disable the video shared ram? Is firewire 400 fast enough for external storage? Etc.
Thanks in advance
m
Does anyone have any advice on using the mini with Leopard server. Is the max ram really 2 gigs? can one disable the video shared ram? Is firewire 400 fast enough for external storage? Etc.
The latest mini will run with 3GB. OWC sells a 3GB kit for it. link
FW 400 is plenty fast enough for everyday stuff and server storage, in my opinion. For large transfers and high end video work, FW 800 or SATA is better.
The latest mini will run with 3GB. OWC sells a 3GB kit for it. link
FW 400 is plenty fast enough for everyday stuff and server storage, in my opinion. For large transfers and high end video work, FW 800 or SATA is better.
On my mini and iMac 24", I can never really tell that big of a mind blowing difference in moving large quantities of files. I thought FW800 would be 2x speed but I don't believe it is. So I think FW 400 would be fine for external storage since it works great with my Final Cut Studio setup.
On my mini and iMac 24", I can never really tell that big of a mind blowing difference in moving large quantities of files. I thought FW800 would be 2x speed but I don't believe it is. So I think FW 400 would be fine for external storage since it works great with my Final Cut Studio setup.
It depends on the device you are writing to. A single hard drive will usually have a maximum transfer rate of 75-100MBps which is 600-800Mbps. FW800 is 800Mbps so can work with the fastest rate the drive can take.
If your drive only reaches 40MBps = 320Mbps then you're not going to see much difference between FW400 and FW800. If on the other hand you target an external RAID setup where transfer rates are 150MBps (1200Mbps) and above, that's where FW800 and eSATA are needed.
http://www.cooldrives.com/newulrafi800.html
Of course, you will be limited by your read speeds if you transfer from a slow drive.
If the mini is being used as a server, aren't you also limited by the transfer speed of your wired or wireless network? I'd think that would be the limiting factor, not the FW400 external drive.
Thanks for the replies.
Could be a non-issue, not sure if database queries are affected more so than other types of disk access. I just want to experiment so I suppose the limitations of the mini would be acceptable until such time as we decide to go live with iCal service. The plan is to migrate to xserve eventually.
Has this been debunked since the Mini is still around and its now 2008?
Will it be updated to have Santa Rosa?
Will it finally get 802.11n?