... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
This old i7 HT quad core will be moved to the side for some mundane tasks.
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
Alan Browne <bitbucket@blackhole.com> writes:
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
MOAR POWER! :-)
On Oct 30, 2023 at 6:24:44 PM PDT, "Alan Browne" <bitbucket@blackhole.com> wrote:
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
This old i7 HT quad core will be moved to the side for some mundane tasks.
Lucky you! Sounds like another significant advance and an excellent time to buy in.
On 2023-10-31 06:46, Bud Frede wrote:
Alan Browne <bitbucket@blackhole.com> writes:
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
MOAR POWER! :-)
I would have preferred the M3 Pro and 48 GB of RAM, but realistically,
this will be more than sufficient for the next 10 years.
And finally I'll have a Mac OS that is compatible with iOS features (esp
in Notes) that I want to use.
The WiFi on this iMac died about 4 months ago, so file drop doesn't work
- nice to have that back.
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
This old i7 HT quad core will be moved to the side for some mundane tasks.
On Oct 30, 2023 at 6:24:44 PM PDT, "Alan Browne" <bitbucket@blackhole.com> wrote:
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
This old i7 HT quad core will be moved to the side for some mundane tasks.
Lucky you! Sounds like another significant advance and an excellent time to buy in.
On 2023-10-31 06:46, Bud Frede wrote:
Alan Browne <bitbucket@blackhole.com> writes:
... only the M3 in the iMac capped at 24 GB of RAM.MOAR POWER! :-)
... so ordered (24 GB + 2TB). Should be here next week.
I would have preferred the M3 Pro and 48 GB of RAM, but realistically,
this will be more than sufficient for the next 10 years.
And finally I'll have a Mac OS that is compatible with iOS features
(esp in Notes) that I want to use.
The WiFi on this iMac died about 4 months ago, so file drop doesn't
work - nice to have that back.
I'm also a fan of Ramdisks when processing video files from format to
format. I currently have a Ramdisk that can go up to 12GB. Happily
it only takes as much memory as it needs (doesn't "block" 12 GB - only
what is needed for the files "in it").
Alan Browne <bitbucket@blackhole.com> writes:
On 2023-10-31 06:46, Bud Frede wrote:
Alan Browne <bitbucket@blackhole.com> writes:
... only the M3 in the iMac capped at 24 GB of RAM.MOAR POWER! :-)
... so ordered (24 GB + 2TB). Should be here next week.
I would have preferred the M3 Pro and 48 GB of RAM, but realistically,
this will be more than sufficient for the next 10 years.
And finally I'll have a Mac OS that is compatible with iOS features
(esp in Notes) that I want to use.
The WiFi on this iMac died about 4 months ago, so file drop doesn't
work - nice to have that back.
AirDrop is one of those features that I know exists (after all, I have
an icon in the sidebar of the Finder for it), but I've never really used much. I'm not sure why, but it just doesn't occur to me to use it.
On Oct 31, 2023 at 6:07:26 AM PDT, "Alan Browne" <bitbucket@blackhole.com> wrote:
On 2023-10-31 06:46, Bud Frede wrote:
Alan Browne <bitbucket@blackhole.com> writes:
... only the M3 in the iMac capped at 24 GB of RAM.
... so ordered (24 GB + 2TB). Should be here next week.
MOAR POWER! :-)
I would have preferred the M3 Pro and 48 GB of RAM, but realistically,
this will be more than sufficient for the next 10 years.
And finally I'll have a Mac OS that is compatible with iOS features (esp
in Notes) that I want to use.
The WiFi on this iMac died about 4 months ago, so file drop doesn't work
- nice to have that back.
What kind of work do you do that demands 48G?
diskutil erasevolume HFS+ 'Ramdisk' `hdiutil attach -nomount
ram://25165824`
Above for 12 GiB (512 byte chunks in the last parameter.
Pro: does not allocate memory until needed.
Con: does not de-allocate as files are deleted. So at some point you
have to eject the drive and re-mount to recover. It should re-use
available space in the RD, but I'm not 100% sure.
On 2023-11-01, Alan Browne <bitbucket@blackhole.com> wrote:
I'm also a fan of Ramdisks when processing video files from format to
format. I currently have a Ramdisk that can go up to 12GB. Happily
it only takes as much memory as it needs (doesn't "block" 12 GB - only
what is needed for the files "in it").
Which RAM disk solution are you using for that?
On 2023-11-01 10:39, Alan Browne wrote:
diskutil erasevolume HFS+ 'Ramdisk' `hdiutil attach -nomount
ram://25165824`
Above for 12 GiB (512 byte chunks in the last parameter.
Pro: does not allocate memory until needed.
Con: does not de-allocate as files are deleted. So at some point you
have to eject the drive and re-mount to recover. It should re-use
available space in the RD, but I'm not 100% sure.
Just tested that - so if one erases a file, and empties the trash, then adding more files re-uses that space w/o allocating more memory.
On 2023-11-01, Alan Browne <bitbucket@blackhole.com> wrote:
On 2023-11-01 10:13, Jolly Roger wrote:
On 2023-11-01, Alan Browne <bitbucket@blackhole.com> wrote:
I'm also a fan of Ramdisks when processing video files from format to
format. I currently have a Ramdisk that can go up to 12GB. Happily
it only takes as much memory as it needs (doesn't "block" 12 GB - only >>>> what is needed for the files "in it").
Which RAM disk solution are you using for that?
Pretty sure I've told you about this in the past, here.
Probably, but I definitely forgot. 🙂
diskutil erasevolume HFS+ 'Ramdisk' `hdiutil attach -nomount ram://25165824` >>
Above for 12 GiB (512 byte chunks in the last parameter.
Pro: does not allocate memory until needed.
Con: does not de-allocate as files are deleted. So at some point you
have to eject the drive and re-mount to recover. It should re-use
available space in the RD, but I'm not 100% sure.
(I have a program running in BG which has a thread to monitor the
ramdisk and if it disappears, it executes the command above).
Thanks. I wasn't aware hdiutil RAM disks behaved that way. That's very
nice default behavior.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 16:15:35 |
| Calls: | 10,389 |
| Files: | 14,061 |
| Messages: | 6,416,935 |