core
/
oga
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
oga/.gitignore

22 lines
280 B
Plaintext
Raw Normal View History

Added Git ignore rules.
2014-02-26 18:51:08 +00:00
yardoc
coverage
pkg
Gemfile.lock
Removed generated lexer/parser. I am a dumbass.
2014-03-25 20:47:40 +00:00
lib/oga/xml/parser.rb
Boilerplate for the XPath lexer.
2014-05-14 06:48:49 +00:00
lib/oga/xpath/lexer.rb
Basic XPath parser setup.
2014-06-01 21:02:28 +00:00
lib/oga/xpath/parser.rb
Basic boilerplate for lexing CSS selectors.
2014-09-16 14:32:57 +00:00
lib/oga/css/lexer.rb
Boilerplate for the XPath lexer.
2014-05-14 06:48:49 +00:00
Initial setup using a C extension. While I've tried to keep Oga pure Ruby for as long as possible the performance of Ragel's Ruby output was not worth the trouble. For example, lexing 10MB of XML would take 5 to 6 seconds at least. Nokogiri on the other hand can parse that same XML into a DOM document in about 300 miliseconds. Such a big performance difference is not acceptable. To work around this the XML/HTML lexer will be implemented in C for MRI/Rubinius and Java for JRuby. For now there's only a C extension as I haven't read up yet on the JRuby API. The end goal is to provide some sort of Ragel "template" that can be used to generate the corresponding C/Java extension code. This would remove the need of duplicating the grammar and associated code. The native extension setup is a hybrid between native and Ruby. The raw Ragel stuff happens in C/Java while the actual logic of actions happens in Ruby. This adds a small amount of overhead but makes it much easier to maintain the lexer. Even with this extra overhead the performance is much better than pure Ruby. The 10MB of XML mentioned above is lexed in about 600 miliseconds. In other words, it's 10 times faster.
2014-05-04 22:25:34 +00:00
lib/liboga.*
Benchmark for lexer lines/second. This benchmark uses a fixture file that is automatically downloaded.
2014-04-17 18:06:24 +00:00
benchmark/fixtures/big.xml
Basic memory profiling setup. This makes it a bit easier to profile memory usage of certain components and plot them using Gnuplot. In the past I would write one-off scripts for this and throw them away, only to figure out I needed them again later on. Profiling samples are written to profile/samples and can be plotted using corresponding Gnuplot scripts found in profile/plot. The latter requires Gnuplot to be installed.
2014-04-29 11:38:56 +00:00
Namespaced the profile directories.
2014-06-12 22:33:53 +00:00
profile/samples/xml/*.txt
profile/samples/xml/*/*.txt
Initial setup using a C extension. While I've tried to keep Oga pure Ruby for as long as possible the performance of Ragel's Ruby output was not worth the trouble. For example, lexing 10MB of XML would take 5 to 6 seconds at least. Nokogiri on the other hand can parse that same XML into a DOM document in about 300 miliseconds. Such a big performance difference is not acceptable. To work around this the XML/HTML lexer will be implemented in C for MRI/Rubinius and Java for JRuby. For now there's only a C extension as I haven't read up yet on the JRuby API. The end goal is to provide some sort of Ragel "template" that can be used to generate the corresponding C/Java extension code. This would remove the need of duplicating the grammar and associated code. The native extension setup is a hybrid between native and Ruby. The raw Ragel stuff happens in C/Java while the actual logic of actions happens in Ruby. This adds a small amount of overhead but makes it much easier to maintain the lexer. Even with this extra overhead the performance is much better than pure Ruby. The 10MB of XML mentioned above is lexed in about 600 miliseconds. In other words, it's 10 times faster.
2014-05-04 22:25:34 +00:00
*.so
tmp
Separated the Java and C ext codebases.
2014-05-06 22:29:10 +00:00
ext/c/lexer.c
ext/java/org/liboga/xml/Lexer.java