IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
in the talloc benchmark. These changes were driven by some cachegrind
profiles, with the biggest improvements coming from inlining some
functions.
I don't think it would be a good idea to start spreading inline and
likely()/unlikely() in other parts of Samba, as the benefit in most
code will be very small, but talloc() is such a speed critical part of
Samba that I think these changes are worthwhile
(This used to be commit 8644708c3f42d249b5d1fd2bde37aeb35288da13)
With ldbbrowse, you can issue searches or browse the database in tree format.
To try it, ensure that "make installswat" is done (it's run by "make install"
so you shouldn't have to do anything special). Run smbd and connect with your
browser to http://localhost:901/apps/samba/utils/ldbbrowse.html
(It looks great in firefox. There's some problem with the layout in IE.
Maybe if I get really really motivated one of these days, I'll look into that.)
There's lots more that could be done with it, but as an example of using
qooxdoo and JSON-RPC, I think it accomplishes its task.
Enjoy!
Derrell
(This used to be commit 0888c7098daefc23738dd47fe1c072516ba55feb)
cost of talloc versus malloc. The size parameter in the test suite was
constantly increasing, leading to a worst case for malloc. It is far
more common to have talloc calls of 100 bytes or lower, so change the
benchmark to reflect this.
This makes talloc look much worse - on my laptop I now get:
talloc: 5615164 ops/sec
malloc: 14337130 ops/sec
I'm working on improving that.
(This used to be commit db273ef4dd6ab58da57bb4b59fb1fd5568585ed8)
by avoiding chain locks on each tdb_fetch() within the search
- use the tdb_get_seqnum() call to avoid re-reading the @BASEINFO
record when it hasn't changed.
These speed up the LOCAL-DBSPEED test for ldb from 7k ops/sec to a bit
over 11k ops/sec
(This used to be commit 1347ad254eb8cd12ce22a5a2a37bec0a0ac8dbf1)
call which does a read lock on all chains. These will be used to make
ldb searches more efficient
(This used to be commit de664ec1f8cf179f1d650563272c0de3f7636e2b)
Issues left for the enterprising developers:
- Selection of the ldb file to open. This version always browses sam.ldb.
- When issuing a search which returns a huge amount of data, firefox times
out while adding the data to the page. The ldb functions on the server
should be upgraded to allow providing a starting offset in the result set,
and a limit of how many results to return. The application can then issue
multiple requests if necessary, to limit the amount of processing needed
to handle any single result set.
Next step for me is to make it look more like a Samba application and less
like a qooxdoo example application. Per Tridge's request, I'll leave the
debug console on the page.
Derrell
(This used to be commit 41ed250e020a0860d1769a3144ec7a153f138b57)
otherwise BASE-DELETE will run all tests
- call ldb_global_init() directly after torture_init()
this isn't strictly needed but looks better
metze
(This used to be commit 0c26c2aefdb603c5ffc87e9c0db0e9b2b34ec0ab)
- set better names on talloc structures in ldb modules, making leaks
easier to track down
(This used to be commit 3bf76db42dc6dde5d71083216dba819869b31c75)
