Make extraction faster (#186)  * Added a no_parallelization mode, to be used while testing. Added a main function for one unittest, to be used in profiling studies    * Small changes to the peak finder function that increases the performance on my sample up to 20 %    * Refactored the cwt coefficients function completely. Another 20 % performance boost...    * Another performance boost in the symmetry looking function. DataFrames are evil    * Again, not use pandas Series. Another boost of 10%...    * Use numpys optimized calculations    * Make the symmetry_looking function an apply function to cache results    * Refactored the AR function and increased its performance by a large factor    * Merged the serial and the per_kind extraction function    * Removed the in_parallel from the name as it doed not make much sense anymore    * Moved the try..except to the place it belongs to


Bring back the Connect to dialog. It still needs some work, but it's  2008-02-21  Vincent Untz  [URL]>  	Bring back the Connect to dialog. It still needs some work, but it's 	better than nothing.  	* libnautilus-private/nautilus-bookmark.c: (nautilus_bookmark_new): 	Actually save the name in the bookmark, instead of forgetting it.  	* src/Makefile.am: Updated to build the connect dialog stuff. 	* src/nautilus-connect-server-dialog-main.c: (show_uri), 	(nautilus_connect_server_dialog_present_uri), (main): 	Port to gio. We use g_app_info_launch_default_for_uri() to open the 	URI, but it will need some more work because it doesn't automount the 	URI. 	* src/nautilus-connect-server-dialog-nonmain.c: 	(nautilus_connect_server_dialog_present_uri): Trivial update. 	* src/nautilus-connect-server-dialog.[ch]: (get_method_description), 	(nautilus_connect_server_dialog_finalize), (connect_to_server), 	(response_callback), (setup_for_type), (display_server_location), 	(nautilus_connect_server_dialog_init), 	(nautilus_connect_server_dialog_new): Port to gio. Add bookmark saving 	feature, to replace the old gnome-vfs network volumes. Remove the 	Browse button, which isn't really needed there. Needs some more polish. 	* src/nautilus-shell-ui.xml: Uncomment the "Connect to" action 	* src/nautilus-window-menus.c: (action_connect_to_server_callback): 	Uncomment code to make use of the dialog  svn path=/trunk/; revision=13797


use array instead of int map for itemTags (#1357)  The itemTags field of the index is only used for findKeys  and findValues. In the findKeys case it loops over all keys  and the simple array is faster. For the findValues case, it  gets the value for a key which is now linear for the number  of tags so will be a bit slower.    The main benefit is it can reduce the memory use considerably  for large indexes. The IntIntHashMap has an overhead of 40  bytes and also allocates an array of 2x the size to avoid  collisions in the map. With a sample index of 10M items this  change reduced the memory size by several GB.


Merge pull request #5 from reducedb/master  optimized cp(), 2x performance increase for large files


cleanup mobile styles, matching style improvement, some ajax fixes


Reorganized the Index and Results page scripts to take better advantage of typescript. The file initialize.ts contains some extensions to the built in types. Improved the reliability of checking if a member exists by using an explicit has own property check. Documented javascript and typescript code. I need to make the generated javascript file initialize.js load on all of the pages.


Update conversation style.  1) No more blue/green for outgoing messages. Just lock or no lock.  2) Use 9-patches instead of shapes for better bubble performance.  3) Use tinting rather than different colored assets.  4) Change outgoing status indicators so that they don't change    width of the bubble as they update.  5) Switch to using ..., check, double-check for pending, sent,    delivered rather than using bubble tone to indicate pending.  // FREEBIE


[PATCH] Reworked function 'get_best_weight()' of Slivers_exuder.h

- Avoid computing incident cells multiple times
- Make it more efficient for P3M3 by not having to use
  tr.min_squared_distance() to compute the distance
  between neighboring vertices


ALSA: hda-intel: Add position_fix quirk for ASUS M2V-MX SE.  With PulseAudio and an application accessing an input device like `gnome-volume-manager` both have high CPU load as reported in [1].  Loading `snd-hda-intel` with `position_fix=1` fixes this issue. Therefore add a quirk for ASUS M2V-MX SE.  The only downside is, when now exiting for example MPlayer when it is playing an audio file a high pitched sound is outputted by the speaker.  $ lspci -vvnn | grep -A10 Audio 20:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)         Subsystem: ASUSTeK Computer Inc. Device [1043:8290]         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-         Latency: 0, Cache Line Size: 64 bytes         Interrupt: pin A routed to IRQ 17         Region 0: Memory at fbffc000 (64-bit, non-prefetchable) [size=16K]         Capabilities: <access denied>         Kernel driver in use: HDA Intel  [1] [URL]/mailarchive/forum.php?thread_name=1265550675.4642.24.camel%40mattotaupa&forum_name=alsa-user


MAGETWO-55729: [Customer] Optimize performance for bundled products with lots of product options - FixedBundleTests refactoring


Performance improvement using in-operator on dicts  Just a small cleanup for the existing occurrences.  Using the in-operator for hash lookups is faster than using .keys() [URL]/questions/29314269/why-do-key-in-dict-and-key-in-dict-keys-have-the-same-output


There is an issue in GPUImageMovie - when instance adds itself as AVPlayerItemVideoOutput delegate: [playerItemOutput setDelegate:self queue:videoProcessingQueue], playerItemOutput doesn't release its delegate when GPUImageMovie instance is deallocating. Later, this results in a method call from the deallocated object (outputSequenceWasFlushed:) and you get the crash. This was found with help of NSZombie detector and I fixed it by adding this in GPUImageMovie dealloc method: [playerItemOutput setDelegate:nil queue:nil];