>I wouldn't worry about the memory so much because the process running
>the compiler is short-lived.
May be that's where my problem is. Often times I do not see memory to be
short-lived, at least not in my windows task manager as I see page file
usage history to go up and up (there are times when it come back
though), ultimately exhausting the virtual memory. I made all the
variables to be local as much as possible in order them to be garbage
collected -- but it appears it does not do that always.
>Regarding speed: It might help if you set some compiler options.
>Especially turning of static analysis. I send an updated version which
>does that.
That again helped some -- speedwise. Thanks.
>Using an XML parser is only interesting if your data actually is XML, I
>think.
Yes, of course, I have to change my input data formatting to XML. That's
why I want to know if the reward will be great before taking this big
undertaking.
>It looks like you want to share a large value between different Oz
> processes.
>Did you try the "obvious" method:
>- On the sender site:
> Ticket = {Connection.offer LargeValue}
> send Ticket through socket
>- On the receiver site:
> receive Ticket from socket
> LargeValue = {Connection.take Ticket}
What do you mean by two different Oz process. I read the input data
string from a socket, which is sent through by a Java process. I read
that through Open.socket read(list: size: len:). Then I call method from
another functor where this string data is compiled to Oz records and
such. So I don't think I am sharing data between two Oz processes?
Thanks again,
Ashis
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
