[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some observations

Hello,

> since we are speaking about internal programming, patches and such things, we
> should take this to the dev list.

I will remove ozone-users from the recipiant list of this post.

[IOException upon connection close]
> Yes. It was (?) a timing problem which should has been fixed. I've added a
> sleep(1000) to ExternalDatabase.close(). This fixed the prblem for me and
> nobody complained so far. Hmm...

Ok. I will try to have a look at it myself. If I am going to be successful
in making contributions to the project, I need to figure out the code sooner
or later anyway.

[NullPointerException upon remote db shutdown]
> > So, is this a known issue?
> 
> No, I normally don't use the admin tool. But I can reproduce the problem.
> 
> Peter, I'm half way done making a new admin interface and front-end. I would
> like to completely drop the old admin API and concentrate on the new one.
> Unfortunately currently I cannot dedicate that much time to this. I could check
> in what I've done so far so that you can have a look. What do you think?

> This would be great.
> 
> Make a diff against the latest CVS and send the patch to the dev list. After
> one or two valuable patches I will give you commit access to the CVS.

Ok. "I'll be back."

[Slowness]
> This one again...
> 
> Peter, it is very slow to call a database object from the client. The socket
> latency is the bottleneck. Creating/deleting your objects inside a database
> omethod (thus inside the server) is around 1000 times faster. Please read docu
> on this.

Yes, I do realize that it is going to be slow to do a remote access. But I
don't understand why Ozone doesn't seem to utilize the CPU fully. In my
experience, client/server apps running locally tend to eat the CPU 100%
(i.e. with no internal socket latency problem).

I *was* able to increase CPU usage slightly though after I discovered the
java process doing most of the work was reniced to level 10 (it's the day
the Linux JVM implements thread priorities). Seti@home (reniced at 20) was
taking a piece of the pie. But even with Seti@home killed, I only get about
20-40% CPU usage, which is strange. I don't think I've ever seen such
behavior before (since everything is local, no waiting on hardware is
involved, so the CPU should get fully utilized (either in user space (Java)
or kernel space (I/O and socket stuff)).

> > * Is development active? Mailinglist activity sure seems to be, but the news
> > on the website has bee sparse for a while :)
> 
> I will remove this f*cking news section. ;) I don't have the time to keep it up
> to date.

Hehe. Ok, got it :)

-- 
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0x5584BD98 or 'Peter Schuller <peter.schuller@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.infidyne.com
E-Mail: peter.schuller@infidyne.com Web: http://scode.infidyne.com