Davs

• About: About my journey with Perl, PerlDancer2, DBIx::Class and testing.

Recent Actions

• Commented on Asynchronous Task Distribution with AnyEvent and ZeroMQ
  No, on the contrary, I like it. Right now i have a similar setup, but the workers are themselves looking into the DB (locking the table while doing that) for jobs to execute.. I guess it won't scale very well..but...
• Commented on Asynchronous Task Distribution with AnyEvent and ZeroMQ
  So in this example you still keep your tasks in the DB, only your workers don't talk to the DB queue? Instead you have one instance of a 'task server', which talks to the DB, selects tasks and sends them...
• Commented on Are Abilities Roles?
  Wow, really good comment about roles vs inheritance!...
• Commented on Eating my own dogfood (parallel tests)
  Based on experience on a relatively small project, using transactions are faster then recreating the database for every single test. Dropping/creating a database is quite faster on SSD or in ramdisk as on HDD. For code, that uses transactions already...
• Commented on The perils of & (and prototypes too!)
  I did not know all of the outputs (haven’t been using prototypes so far). Great article!...
• Commented on My database involved testing setup
  Wow I think I managed to fix it and cut down test execution time to 15sec. The problem was in test, where I would do some DB operations in a separate scope. Making everything to happen in the same scope...
• Commented on My database involved testing setup
  I've been experimenting with transactions further. It IS fast (around 14sec) but I keep getting mostly 1 error, but sometimes more, which is I think due to race conditions or something (long story short it does not like the fact,...
• Commented on My database involved testing setup
  Actually, I've tried transactions, after getting the schema, I called schema->txn_begin and before done_testing() I put schema->txn_rollback. When running test sequentually, i took about 33+ sec, which is quite nice. But I could not get it to work when running...
• Commented on My database involved testing setup
  @craig.treptow thanks for that, it is very useful @domm well, for this project I am kinda stuck with mysql. With that transaction you may be right, I'll have to test it. How would it go basically? I can not think...
• Posted My database involved testing setup to Davs

  Hi!

  Today I'd like to show you my testing setup which involves database testing. Hopefully it can help someone out or maybe someone could suggest me better ways of doing things.

  First of all, having all the tests in the root of the 't/' directory got too messy, so I'm using mostly …

• Posted Simplifying imports (mainly in tests) to Davs

  During test writing often I find myself having to use a lot of modules and setting up various things that should be common for all of my tests in a given project. In some examples it may get ugly and I really don't like having a ~30 lines long setup in every single test file of mine. After some…

• Posted Post #1 to Davs

  Hello everyone, this is my first post here.
  I …

Comment Threads

• dotandimet commented on The perils of & (and prototypes too!)

  There’s a good example of the difference between func() and &func in this regression I reported in the Perl 5.18.0 debugger: You could no longer see the value of @_ in the debugger, because this line: eval { &DB::save }; was replaced with this: eval { DB::save() }; https://rt.perl.org/Public/Bug/Display.html?id=118169

• davewood commented on Asynchronous Task Distribution with AnyEvent and ZeroMQ

  Thats correct.

  Now I can scale the worker processes while still having information about the job state in the DB.

  Do you see anything wrong with that?

• davewood commented on Asynchronous Task Distribution with AnyEvent and ZeroMQ

  send me a message if you are interested in more code. the example code used in this blog post is stripped down so it's easier to read..