NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Ilya user type tweak (Score:1)
I mentioned this on #perl6, but I think you missed it -- the high-performance user ("Ilya") may be doing bandwidth-intensive stuff as well -- it's important then to have efficient access to packed data streams.
This becomes especially important when each data element requires very little computation, but there are a LOT of data elements to go through.
Hmmm, perhaps this should be a new user type . . . .
Re:Ilya user type tweak (Score:1)
Perhaps you could contribute an "Ilya Prime" sub-profile?
Re:Ilya user type tweak (Score:1)
=== docs/req/model_users.pod
=====================================================
--- docs/req/model_users.pod (revision 13090)
+++ docs/req/model_users.pod (local)
@@ -103,6 +103,38 @@
a favorite feature set and stick with it
+=head2 "Ilya Prime": Intensive Memory Bandwidth User
+
+Ilya Prime writes high-performance memory bandwidth-bound code,
+typically involving either very large packed arrays or "touch once"
+streaming algorithms that make CPU caches near-useless.
+
+Ilya Prime:
+
+* cares about performance to exclusion of most other factors
+* needs to be able to efficiently exchange large data sets with
+ special-purpose libraries, such as audio and video codecs
+* needs to be able to efficiently work with packed data
+* doesn't care about PBC one way or the other
+
+
+=head2 "Ilya Double Prime": Intensive Threading User
+
+Ilya Prime writes high-performance threading-intensive code,
+typically involving simulations, server implementations, or
+simply efficient use of a heavily threaded CPU architecture.
+
+Ilya Prime:
+
+* cares about performance, memory footprint, thread-safe
+ correctness, and possibly security/DOS prevention APIs
+* needs to be able to create and destroy large numbers of
+ threads rapidly
+* needs to be able to transit data between threads rapidly
+* cares about PBC only inasmuch as it affects threading
+ performance and overall process memory footprint
+
+
=head2 "Magpie": Lover of shiny things
Magpie sees something shiny -- a new runtime, or a new language, or
Reply to This
Parent
Re:Ilya user type tweak (Score:1)