everburning

I was reading through my previous entries and came across the following numbers

Ewl_Test and opening all test windows
 21727 dsinclai  15   0 68360  15m 4304 S  0.0  1.5   0:09.73 ewl_test

The ewl_filedialog on a directory with 3000 entries
  6871 dsinclai  25   0  115m  63m 4104 S  0.0  6.4   0:04.62 ewl_test

These were from when I did the conversion of the callback chains to be an array. So, I decided to check it out today:

Ewl_Test and opening all test windows
 6157 zero      15   0 24928  18m 5148 S 16.6  1.2   0:09.66 ewl_test    

The ewl_filedialog on a directory with 3000 entries
 6130 zero      16   0 22948  16m 4788 S 21.3  1.1   0:04.74 ewl_test

(Looking at the first run, it was done on my amd64 box at work, the 2nd set on my intel box at home, so not sure if that would effect the numbers much or not.)

Your probably looking at the Ewl_Test run and seeing the numbers went up. There are actually more tests in there now. The text editor being one of them. Other tests have had more widgets added to test other things, so it's actually testing more stuff.

But, if you look at the 3000 entry filedialog, there's a huge amount of savings in there. With the added benefit that the scrolling is faster. Three cheers for Nathans object cache in EWL.

So, I spent some more time working on the Ewl_Text widget. I've managed to get the selections to show again after a lot more effort then I want to think about. There are still a few small issues with them that need to be worked out, but their pretty close again. Which is nice after all the effort to get them there.

I think next up is getting the cursor to react correctly to the end of the line. After that I'll probably let text sit for a while and digest. There are issues with overlapping styles and fonts and things, but aren't killers at the moment as I think only the 'text editor' test uses those features, heh.

After I move off of the text stuff I think I'm going to break the Ewl_Filedialog API a bunch. My current plan is to take what is current Ewl_Fileselector and move that to Ewl_Filelist. I will then move Ewl_Filedialog to be Ewl_Fileselector. I will then make a new Ewl_Filedialog which is _actually_ a dialog window, oh, the horror. Once that's done we may do some remodeling of the filedialog. We've been looking around to see whats out there and currently the OSX one seems to be catching the most interest. We'll have to see, that's a bit of a ways off. But, I want to get this API break out of the way as we're getting a few more uses of EWL and I want the API to be at least pseudo-stable for them.

We've been making some pretty good progress in the memory usage and allocation department lately. With the last round of changes raster put into evas starting the ewl_test app as dropped from around 70k allocations to 22k. We've also dropped a shit tonne of memory usage over the last few months as we've gone back and analyzed data structures and re-written chunks of code to be more streamlined.

So, all in all, this sucker is shaping up nicely.

So, I've been running ZFS on my server for a while and have continuously bumped into a problem where root was getting squashed. I tried looking everywhere I could think of for the answer but kept coming up blank. So, I broke down and asked benr and he pointed me in the right direction.

I had been trying to find things like the 'sharenfs' man page, which is the name of the zfs property. In fact, the page I wanted was 'share_nfs' and specifically the 'root=' option. So, in the end I ended up doing something along the lines of:


zfs set sharenfs='root=@192.168.1/24' oni/data
zfs set sharenfs='root=@192.168.1/24' oni/media
zfs unshare -a
zfs share -a


And everything seems to be good to go. I even managed to the the unshare/share without my mp3's skipping.

The Childs Play charity that the guys over at Penny Arcade run is supporting the Sick Kids hospital in Toronto this year, so I decided to donate a PS2 and a copy of 'We Love Katamari'. I think I filled everything in correctly so they'll end up at the hospital. It's a good cause, go give them your money.

I got a copy of 'We Love Katamari' today, and played a few levels, it's pretty addicting, rolling your ball around and trying to pick up as much stuff as you can find. It's also got to be one of the trippiest games out there. It's just plain wacky. If you haven't tried it grab a copy and get rolling.

I've been playing with Solaris a bunch lately. I've got Solaris Express Build 26 installed on my laptop (for some reason build 27 won't boot) and I'm in the process of grabbing the OpenSolaris source from the genunix subversion repo and hopefully (I've already bitch this once) BFUing the stuff I build onto there.

I've also managed to shoehorn build 27 onto my AMD64 box that I use as a server. Man did I learn a lot I didn't know about Solaris in that exercise (and used a floppy disk for probably the first time in 5 years). After a lot of fighting, figuring out _how_ to use a floppy in Solaris (which involved a detour into svcadm), getting my network drivers correct (note, if you have a marvell gigabit ethernet you'll need to go and download the drivers from the website as the bundled SK98sol drivers won't work. You'll also need to remove the SK98sol drivers, install the new ones, do a update_drv -a -i “pcixxxx,xxx” skge and reboot. It was the reboot that caught me up for quite a while). I've now got a 530gb zfs pool running on the box. I've got 2 more hard drives to put in (which would take it to 930gb) but I don't think my SATA controller is support so they probably won't work correctly. Not sure how to get around that at the moment.

But I must say, zfs is pretty sweet. It took me all of (after screwing around and formatting a drive when I didn't have to) 30 minutes to get the 4 drives into a pool, create file systems in the pool and nfs share those file systems.