[#389739] Ruby Challenge — teresa nuagen <unguyen90@...>

Here is a ruby challenge for all you computer science lovers out there,

22 messages 2011/11/05
[#389769] Re: Ruby Challenge — "Jonan S." <jonanscheffler@...> 2011/11/05

Totally unrelated to any husker computer science programs right? Like

[#389905] Re: Ruby Challenge — Stephen Ramsay <sramsay.unl@...> 2011/11/09

Jonan S. wrote in post #1030330:

[#389907] Re: Ruby Challenge — aseret nuagen <unguyen90@...> 2011/11/09

> You mean like the professor for the course? Because that would be me .

[#389915] Re: Ruby Challenge — Robert Klemme <shortcutter@...> 2011/11/09

On Wed, Nov 9, 2011 at 4:52 AM, aseret nuagen <unguyen90@aim.com> wrote:

[#389792] Tricky DSL, how to do it? — Intransition <transfire@...>

I'd want to write a DSL such that a surface method_missing catches

18 messages 2011/11/06

[#389858] Compiling Ruby Inline C code - resolving errors — Martin Hansen <mail@...>

I am trying to get this Ruby inline C code http://pastie.org/2825882 to

12 messages 2011/11/08

[#389928] Forming a Ruby meetup group... — "Darryl L. Pierce" <mcpierce@...>

Where I work we have a local Ruby group that used to meet up, until the

12 messages 2011/11/09

[#389950] The faster way to read files — "Noé Alejandro" <casanejo@...>

Does anybody know which is the fastest way to read a file? Lets say

18 messages 2011/11/09

[#390064] referring to version numbers in a gem — Chad Perrin <code@...>

How do I specify and access a gem's version number within the code of the

28 messages 2011/11/11

[#390238] RVM problem, plz help — Misha Ognev <b1368810@...>

Hi, I have this problem:

15 messages 2011/11/16

[#390308] any command line tools for querying yaml files — Rahul Kumar <sentinel1879@...>

(Sorry, this is not exactly a ruby question).

11 messages 2011/11/18

[#390338] Newbie - cmd question — Otto Dydakt <ottodydakt@...>

I've literally JUST downloaded ruby from rubyinstaller.org.

21 messages 2011/11/19
[#390342] Re: Newbie - cmd question — Otto Dydakt <ottodydakt@...> 2011/11/19

OK thank you, I uninstalled & reinstalled, checking the three boxes at

[#390343] Re: Newbie - cmd question — "Ian M. Asaff" <ian.asaff@...> 2011/11/19

did you type "irb" first to bring up the ruby command prompt?

[#391154] Re: Newbie - cmd question — "Hussain A." <hahmad@...> 2011/12/12

Hi all,

[#391165] Re: Newbie - cmd question — Luis Lavena <luislavena@...> 2011/12/12

Hussain A. wrote in post #1036281:

[#390374] Principle of Best Principles — Intransition <transfire@...>

I seem to run into a couple of design issue a lot and I never know what is

16 messages 2011/11/20

[#390396] how to call Function argument into another ruby script. — hari mahesh <harismahesh@...>

Consider I have a ruby file called library.rb.

10 messages 2011/11/21

[#390496] How to make 1.9.2 my default version using RVM — Fily Salas <fs_tigre@...>

Hi,

25 messages 2011/11/24

[#390535] Is high-speed sorting impossible with Ruby? — "Gaurav C." <chande.gaurav@...>

Well, first of all, I'm new to Ruby, and to this forum. So, hello. :)

39 messages 2011/11/25
[#390580] Re: Is high-speed sorting impossible with Ruby? — Joao Pedrosa <joaopedrosa@...> 2011/11/27

Hi,

[#390593] Re: Is high-speed sorting impossible with Ruby? — "Gaurav C." <chande.gaurav@...> 2011/11/27

Joao Pedrosa wrote in post #1033884:

[#390600] Re: Is high-speed sorting impossible with Ruby? — Douglas Seifert <doug@...> 2011/11/27

A big gain can be had by disabling the garbage collector. Here is my best

[#390601] Re: Is high-speed sorting impossible with Ruby? — Douglas Seifert <doug@...> 2011/11/27

I've thrown various solutions up on github here:

[#390650] Loading a faulty ruby file - forcing this — Marc Heiler <shevegen@...>

Hi.

10 messages 2011/11/29

[#390689] Stupid question — James Gallagher <lollyproductions@...>

Hi everyone.

22 messages 2011/11/30

Re: Is high-speed sorting impossible with Ruby?

From: Douglas Seifert <doug@...>
Date: 2011-11-28 02:20:38 UTC
List: ruby-talk #390614
>
> So I'm reading your code and trying to figure out what cracked the
>
problem. Could you share some insights? Why to disable the GC? What idea
> should one take away from other parts of your code?
>

Here is the code again.  I will put comments inline to try to give insight
into what I was thinking:


> > GC.disable
>

This is a real cheat.  By turning off the garbage collector, you don't let
the ruby interpreter reclaim memory by deallocating objects that are no
longer used.  Normally, the Ruby interpreter periodically runs a garbage
collection loop where it runs through all allocated objects and if they are
not referenced any more, may free the memory, giving it back to the OS.
 During the loop, your code will not run.  By turning it off, your program
can consume lots of memory, especially if it creates many throw away
objects.


> > n = STDIN.gets.to_i
> > a = Array.new(1e6+1) {|n| ""}
>

The above creates an Array of 1,000,001 slots.  The block syntax lets you
provide a default object dynamically.  The first time you reference a
particular index in the array, the block is called to allocate the default
object at that position.


> > while n > 0
> >   i_str = STDIN.gets
> >   i = i_str.to_i
> >   a[i] << i_str
>

Here we append a string representation of the value read to string at the
position in the index.  We are creating garbage objects here.  Each string
produced by STDIN.gets, after it is appended (copied) to the string at
position i in the array, is no longer referenced anywhere.  Since we turned
off the garbage collector, the memory used by this string just hangs around
in the ruby process.

Another interesting thing to note: Thanks to the way we created the array
above, we start out with a new empty string for each position referenced in
the array.  If we had made the mistake of creating it like this:

a = Array.new(1e6+1, "")

we would have an array where every position gets the same empty string as
the default value.  We would thus append all values in the input to the
same string ... not what we intend.


> >   n -= 1
> > end
> >
> > n = 0
> > while n < 1_000_001
> >   STDOUT.write a[n]
> >   n += 1
> > end
>

This just goes through the array and writes out the value at the position.
 If we had used the wrong Array initializer, we would basically be
outputting the entire input set 1,000,000 times.

Hope that helps ...

-Doug

In This Thread