From: richard schneeman <richard.schneeman@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: [PATCH] conditionalget: avoid const lookup in case/when
Date: Mon, 6 Oct 2014 13:00:17 -0700 (PDT) [thread overview]
Message-ID: <e81ed0c2-2b98-48b8-84b4-0e55eefe8c78@googlegroups.com> (raw)
In-Reply-To: <CABGa_T_FL5Rfx3nk91Q4jGZxu_vWaY-aHqin57df4k8PL1N9Cw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Thank you Eric indeed! It took me a little while to figure out, so i
thought I would mention, you can reference git commits for ruby/ruby by
running:
```
$ git log --grep "trunk@44058"
```
That first SVN commit is
*https://github.com/ruby/ruby/commit/779ae78995977305aa5aec9cb5b562dcf54c22e7*
The second commit is:
*https://github.com/ruby/ruby/commit/58f800a278b8b70463f4afdbb23a918d8ab441ff*
Eric's proposal: *https://bugs.ruby-lang.org/issues/9425*
I agree that the patch should one day be unnecessary, In the mean time i'm
happy to get faster execution while we wait. I was talking with Koichi
about how or if we might optimize so we could write "normal" ruby code and
still have it run as memory efficient and fast as using constants. He
showed me that this string de-duplication feature was in 2.2, though I was
having a hard time finding the commits. Thank you Eric for listing them.
In my research it was also pointed out that string de-duplication was added
to JVM-8 *http://java-performance.info/java-string-deduplication/*. I think
it's great that Ruby has already started to make string de-duplication
optimizations.
Thanks for the perf help and again for the links!
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Type: text/html, Size: 2961 bytes --]
next prev parent reply other threads:[~2014-10-06 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 20:08 Less allocated objects on each request Eric Wong
2014-10-05 8:15 ` [PATCH] conditionalget: avoid const lookup in case/when Eric Wong
2014-10-05 21:37 ` James Tucker
2014-10-06 20:00 ` richard schneeman [this message]
2016-05-12 3:04 ` Less allocated objects on each request Eric Wong
2016-05-12 16:54 ` Aaron Patterson
2016-05-12 17:01 ` richard schneeman
2016-05-13 23:41 ` Eric Wong
2016-06-17 19:43 ` richard schneeman
2016-06-17 21:00 ` Aaron Patterson
2016-06-17 23:12 ` Eric Wong
2016-06-17 23:19 ` Aaron Patterson
2016-06-17 23:43 ` Eric Wong
2014-10-05 21:31 ` James Tucker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e81ed0c2-2b98-48b8-84b4-0e55eefe8c78@googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).