[#5322] O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...>

I just did some benchmarks on push, pop, shift, and unshift

24 messages 2005/07/01
[#5338] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/02

On Fri, 1 Jul 2005, Eric Mahurin wrote:

[#5348] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/02

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5357] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sat, 2 Jul 2005, Eric Mahurin wrote:

[#5359] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5361] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sun, 3 Jul 2005, Eric Mahurin wrote:

[#5362] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5365] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5367] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/04

--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

[#5368] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5372] Re: O(1) performance for insertions/deletions at the front of an Array/String — Florian Gro<florgro@...> 2005/07/04

Yukihiro Matsumoto wrote:

[#5420] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...>

Sydney, an experimental ruby interpreter, has been released!

15 messages 2005/07/11
[#5424] Re: [ANN] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...> 2005/07/12

Thanks everyone for the feedback so far!

Re: GC tweak

From: Stefan Kaes <skaes@...>
Date: 2005-07-14 18:18:52 UTC
List: ruby-core #5463
Mathieu Bouchard wrote:

>On Thu, 14 Jul 2005, Stefan Kaes wrote:
>  
>
>>Any comments?
>>    
>>
>
>isn't the following a bit more straightforward?
>
>static void set_gc_param(int *var, const char *name) {
>    char *p = getenv(name);
>    if (p) {
>      int i = atoi(p);
>      if (i>0) *var = i;
>    }
>}
>static void set_gc_parameters(void) {
>    set_gc_param(heap_min_slots, "RUBY_HEAP_MIN_SLOTS");
>    set_gc_param(heap_free_min,  "RUBY_HEAP_FREE_MIN");
>    set_gc_param(heaps_increment,"RUBY_HEAP_INCREMENT");
>    set_gc_param(gc_stats,       "RUBY_GC_STATS");
>    set_gc_param(malloc_limit,   "RUBY_GC_MALLOC_LIMIT");
>    heap_slots = heap_min_slots;
>}
>
>  
>
Certainly. If you make it "&heap_min_slots" etc. in the calls to 
set_gc_param ;-)

But then you will loose the ability to do any option specific processing.

-- stefan

In This Thread

Prev Next