profiler

I would like to measure the time elapsed to evaluate a block of code in a Python program, possibly separating between user cpu time, system cpu time and elapsed time. I know the timeit module, but I have many self-written functions and it is not very easy to pass them in the setup process. I would rather have something that could be used like: #up to here I have done something.... start_counting() #or whatever command used to mark that I want to measure #the time elapsed in the next rows # code I want to evaluate user,system,elapsed = stop_counting() #or whatever command says: #stop the timer

i wonder if there is something similar to Sql Profiler for Sql Server Compact Edition? i use SqlCE as backend for a desktop application and it would be really great to have something like sql profiler for this embedded database. or at least something simliar to the NHibernate show_sql feature... any ideas? thanks j. Sam Saffron The only tested solution I know of that could solve this problem is Altiris Profiler which is a tool I designed at my previous job, but is closed source and not-for-sale. The way you would hook it in, is by creating a factory for your commands and proxing them for

Is it possible to monitor what is happening to an Access MDB (ie. what SQL queries are being executed against it), in the same way as you would use SQL Profiler for the SQL Server? I need logs of actual queries being called. Oleg The answer depend on the technology used from the client which use MDB. There are different tracing settings which you can configure in HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC http://office.microsoft.com/en-us/access/HP010321641033.aspx . If you use OLEDB to access MDB from SQL Server you can use DBCC TRACEON (see http://msdn.microsoft.com/en-us

Everyone always says to profile your program before performing optimizations but no-one ever describes how to do so. What are your practices for profiling C code? Alex Martelli Using gcc , I compile and link with -pg (as explained e.g. here ), then continue by running the program (according to the principles also suggested at that URL) and using gprof . The tools will vary if you're using different compilers &c, but the URL is still recommended, even then, for the parts that are about general ideas on how and why to profile your code. If you are using Linux, then I recommend the combination of