« Return to Thread: Scala and the 64 bit opportunity
Re: [scala] Scala and the 64 bit opportunity
by David Pollak
::
Rate this Message:
First, Scala runs on the JVM, so it's got the same limitations as Java
and thus, indexing Array beyond Int is not going to happen without a
huge performance hit.
Second, I've written a fair number of Scala and Java apps that deal with
> 8GB of data. I've never had a need for > Int addressing.
Third, processors aren't getting any faster, so having huge blocks of
stuff that needs to be GCed is a huge lose.
Forth, the JVM's concurrency semantics (Monitor Enter/Exit) do not scale
to large scale data blocks (too much lock contention.)
Personally, I think that Scala has solved a lot of the issues associated
with huge data sets.
The functional/immutable constructs (e.g., List) lend themselves to much
better small-to-large abstractions. They lead to much better concurrent
abstractions. Plus, Scala Actors are a much better way of dealing with
isolation of data into reasonable computational units.
jherber wrote:
> Just watched Javapolis 07 roundtable discussion where Neil Gafter (@Google)
> says they are running into 32bit issues today in Java's libraries (int
> indexes) and expects regular applications to start hitting them soon.
>
> Given nearly all server (and many notebook) chips have been 64 bit enabled
> for years; the 64 bit operating systems adoption tipping point appears to be
> essentially here; and > 4GB of ram will soon be common for servers and
> notebooks: How is Scala going to address these issues where integer types
> are used all over the place for indexes, start, and length signatures and
> internals on built in data types (Lists, etc)?
>
> From a pure technical marketing standpoint, a nascent language not ready for
> the larger memory solution space could hurt it's adoption in coming years.
>
> Curious to see what the language team and other developers think.
>
>
and thus, indexing Array beyond Int is not going to happen without a
huge performance hit.
Second, I've written a fair number of Scala and Java apps that deal with
> 8GB of data. I've never had a need for > Int addressing.
Third, processors aren't getting any faster, so having huge blocks of
stuff that needs to be GCed is a huge lose.
Forth, the JVM's concurrency semantics (Monitor Enter/Exit) do not scale
to large scale data blocks (too much lock contention.)
Personally, I think that Scala has solved a lot of the issues associated
with huge data sets.
The functional/immutable constructs (e.g., List) lend themselves to much
better small-to-large abstractions. They lead to much better concurrent
abstractions. Plus, Scala Actors are a much better way of dealing with
isolation of data into reasonable computational units.
jherber wrote:
> Just watched Javapolis 07 roundtable discussion where Neil Gafter (@Google)
> says they are running into 32bit issues today in Java's libraries (int
> indexes) and expects regular applications to start hitting them soon.
>
> Given nearly all server (and many notebook) chips have been 64 bit enabled
> for years; the 64 bit operating systems adoption tipping point appears to be
> essentially here; and > 4GB of ram will soon be common for servers and
> notebooks: How is Scala going to address these issues where integer types
> are used all over the place for indexes, start, and length signatures and
> internals on built in data types (Lists, etc)?
>
> From a pure technical marketing standpoint, a nascent language not ready for
> the larger memory solution space could hurt it's adoption in coming years.
>
> Curious to see what the language team and other developers think.
>
>
« Return to Thread: Scala and the 64 bit opportunity
| Free embeddable forum powered by Nabble | Forum Help |
