>
> (
> I have not benchmarked this new code, but it should run much faster.
> Timothy
>
>
>
> On Fri, Nov 29, 2013 at 5:04 PM, kandre
> > wrote:
>
>> Here is the gist: https://gist.github.com/anonymous/7713596
>> Please not that there's no or
Maybe I'll just use my simpy models for now and wait for clj-sim ;)
Any chance of sharing?
Cheers
Andreas
On Saturday, 30 November 2013 15:40:10 UTC+10:30, Ben Mabey wrote:
>
> On 11/29/13, 9:16 PM, Cedric Greevey wrote:
>
> On Fri, Nov 29, 2013 at 11:03 PM, Ben Mabey
> > wrote:
>
>> On 11/2
I am simulation a network of roads, sources and sinks of materials, and
trucks hauling between sinks and sources. There is not much of a workload -
the complexity arises from having hundreds of trucks going through their
states and queuing at the sources/sinks. So the bulk of the simulation
con
n Saturday, 30 November 2013 09:31:08 UTC+10:30, kandre wrote:
>
> I think I can provide you with a little code snipped.
> I am talking about the very basic car example (driving->parking->driving).
> Running the sim using core.async takes about 1s for 10^5 steps whereas the
>
turday, 30 November 2013 09:22:22 UTC+10:30, Ben Mabey wrote:
>
> On Fri Nov 29 14:13:16 2013, kandre wrote:
> > Thanks for all the replies. I accidentally left out the close! When I
> contrived the example. I am using core.async for a discrete event
> simulation system. There a
Thanks for all the replies. I accidentally left out the close! When I contrived
the example. I am using core.async for a discrete event simulation system.
There are hundreds of go blocks all doing little but putting a sequence of
events onto a channel and one go block advancing taking these even
Hi there,
I've started playing with core.async but I am not sure if I'm using it the
way it was intended to.
Running a simple benchmark with two go-blocks (one writing an event to a
channel, the other one reading it out) seems quite slow:
(time (let [c (chan 100) stop (chan)]
(go
(dotime
