Recherche avancée

Sur d’autres sites (9277)

• A/B Testing Platform for Piwik Analytics

  10 novembre 2016, par InnoCraft — Plugins, Press Releases

  We are very excited to launch A/B Testing – a powerful new product designed to help you maximise your success and increase your conversions.

  What is A/B Testing and why is it so important ?

  Experimenting with A/B Testing is an important marketing strategy that goes a long way in maximising your conversions.

  With A/B Testing you can start improving your conversions and sales in your existing website or app by creating different versions of a web page or mobile app screen to find out how to modify your website to optimize business success.

  How does A/B Testing work ?

  To explain how A/B Testing works, let’s take an example. Imagine one of your most important landing pages has been redesigned to hopefully get more email signups. Now you need to make sure the new version is “better” than the current version, or at least does result in less conversions. To compare the performance of these two versions, you can then run an A/B test whereby the A/B testing product tells you whether the redesigned version is producing more email signups compared to the original version.

  How it works is that visitors on your website during the experiment will see a randomly chosen version (variation) and A/B Testing makes sure that your users will always see the same variation for all subsequent visits. The behaviour and goals converted by each user is measured continuously by Piwik A/B Testing. The beautifully designed and easy to use dashboard shows how each variation impacts your success metrics such as conversions, sales or page views.

  When the A/B test is complete, you will then know which is the winning version getting you closer to reaching your goals ! A/B Testing includes an advanced statistical analysis engine to provide a reliable indicator of which of your versions is actually improving your bottom line.

  Examples of successful A/B tests

  Below are a just a few interesting A/B tests results from the article 7 Dead-Simple A/B Tests You Should Run on Your Homepage (HubSpot).

  Increase click on CTA button by 21%

  

  We actually conducted an A/B test on button color and found that changing the CTA button from green to red increased clicks by 21%. In the world of website optimization, that’s huge !

  47.7% more clicks on the navigation bar

  

  An A/B test comparing the phrases used on the navigation bar discovered that the menu link “How It Works” earned 47.7% more clicks than “Why Use Us.”

  5% more conversions using a different image

  

  Highrise, a small business CRM, A/B tested their website’s imagery by featuring two different people – Jocelyn on the left, and Michael on the right. They found Michael helped improve conversions by almost 5%.

  Changing the headline to increase conversions by 38%

  

  WhichTestWon ran an A/B test on AwayFind’s homepage and found that Version B increased signups by 38%. This could be because the headline is more concise and the subheader includes bolded words to clearly communicate the product’s value

  Where do I start testing ?

  Your testing strategy is tied to your overall business strategy. What do you want people to achieve on your website ? What are the goals that you want your users to convert ? What are your one or two Key Performance Indicators, and what are your targets for these KPIs ?

  When you start thinking of improving your targets you can begin by looking at the most important parts that can be improved :

  • What are your call to actions ?
  • Which are your most popular pages, and landing pages ?
  • What elements of my website is above the fold and can be seen by all visitors within a few seconds ?

  How do I get A/B Testing ?

  All premium plugins come with our 14 day money back guarantee and 1-click installation & updates. Customers get all product updates for free.

  Learn more about A/B Testing Get it now on the Marketplace

  A/B Testing is available for purchase and download on the Marketplace.

  If you are not using Piwik yet, you can also signup for a free trial of Piwik Cloud (including A/B Testing !).

  Have a question about this product ? Get in touch.

• Revision c5443fc881 : Fix decoder mismatch in sub-pixel SSSE3 intrinsic filters In 8-tap filtering, t

  23 mai 2014, par Yunqing Wang

  Changed Paths :
   Modify /vp9/common/x86/vp9_asm_stubs.c

  
   Modify /vp9/common/x86/vp9_subpixel_8t_intrin_ssse3.c

  
  
  Fix decoder mismatch in sub-pixel SSSE3 intrinsic filters

  In 8-tap filtering, to guarantee the intermediate results fit in
  16 bits, the order of accumulating the products needs to be done
  correctly, and the largest product should be added last. This
  patch fixed the problem using the method in commit "Correct ssse3
  8/16-pixel wide sub-pixel filter calculation".

  Change-Id : I79d0ad60c057b15011ece84cda9648eee0809423

• ffmpeg GPU use cuvid with hwdownload will never finished, Appeared only recently

  28 mai 2020, par tags bt

  ffmpeg :

  



  ffmpeg version N-97331-g10a68cc Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  configuration: --pkg-config-flags=--static --prefix=/usr/local/ffmpeg --bindir=/usr/local/ffmpeg/bin --extra-cflags='-I /usr/local/ffmpeg/include -I /usr/local/cuda/include/' --extra-ldflags='-L /usr/local/ffmpeg/lib -L /usr/local/cuda/lib64/' --extra-libs=-lpthread --enable-cuda --enable-cuda-nvcc --enable-cuvid --enable-libnpp --enable-gpl --enable-libass --enable-libfdk-aac --enable-vaapi --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree --enable-libaom --enable-nvenc


  



  nvidia-msi

  



  +-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.82       Driver Version: 440.82       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1080    Off  | 00000000:02:00.0 Off |                  N/A |
|  0%   51C    P8    13W / 200W |     18MiB /  8119MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     23224      C   ffmpeg                                         8MiB |
+-----------------------------------------------------------------------------+



  



  if i use this command :

  



  ffmpeg -re -threads 0 -loglevel debug -hwaccel cuvid -hwaccel_output_format cuda -i 1.mp4 -c:v h264_nvenc -c:a aac -ac 2 -b:a 128k -strict -2 -filter_complex "[0:v]scale_npp=1280:-2" ouzz2t.mp4


  



  it will very fast.

  



  but if i use this command :

  



  ffmpeg -re -threads 0 -loglevel debug -vsync 0 -hwaccel cuvid -hwaccel_output_format cuda -hwaccel_device intel -i 1.mp4 -c:v h264_nvenc -c:a aac -ac 2 -b:a 128k -strict -2 -filter_complex "[0:v]scale_npp=1280:-2:format=yuv420p[tmp],[tmp]hwdownload,format=yuv420" ouzz2t.mp4


  



  it will never finished, one 40MB mp4 will transcode 44 minutes and not finished.

  



  as you see

  



  +-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     23224      C   ffmpeg                                         8MiB |
+-----------------------------------------------------------------------------+


  



  it will only use GPU memory 8mib.

  



  and top will show :
enter image description here

  



  delug log :

  



  [AVHWDeviceContext @ 0x561cfaef92c0] Loaded lib: libcuda.so.1
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuInit
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceGetCount
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceGet
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceGetAttribute
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceGetName
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceComputeCapability
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxCreate_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxSetLimit
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxPushCurrent_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxPopCurrent_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxDestroy_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemAlloc_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemAllocPitch_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemsetD8Async
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemFree_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemcpy2D_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMemcpy2DAsync_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGetErrorName
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGetErrorString
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuCtxGetDevice
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDevicePrimaryCtxRetain
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDevicePrimaryCtxRelease
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDevicePrimaryCtxSetFlags
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDevicePrimaryCtxGetState
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDevicePrimaryCtxReset
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuStreamCreate
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuStreamQuery
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuStreamSynchronize
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuStreamDestroy_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuStreamAddCallback
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuEventCreate
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuEventDestroy_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuEventSynchronize
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuEventQuery
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuEventRecord
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuLaunchKernel
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuModuleLoadData
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuModuleUnload
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuModuleGetFunction
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuTexObjectCreate
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuTexObjectDestroy
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGLGetDevices_v2
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGraphicsGLRegisterImage
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGraphicsUnregisterResource
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGraphicsMapResources
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGraphicsUnmapResources
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuGraphicsSubResourceGetMappedArray
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDeviceGetUuid
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuImportExternalMemory
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDestroyExternalMemory
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuExternalMemoryGetMappedBuffer
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuExternalMemoryGetMappedMipmappedArray
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMipmappedArrayGetLevel
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuMipmappedArrayDestroy
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuImportExternalSemaphore
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuDestroyExternalSemaphore
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuSignalExternalSemaphoresAsync
[AVHWDeviceContext @ 0x561cfaef92c0] Loaded sym: cuWaitExternalSemaphoresAsync



  



  Stop at Loaded sym : cuWaitExternalSemaphoresAsync, and ffmpeg will always 100% cpu and never finished.

  



  Appeared only recently, last week it work fine, but today it work worse.

  



  somebody know what happen to me ?