Hi
user
Admin Login:
Username:
Password:
Name:
Postgres Performance for Humans
--client
fosdem
--show
fosdem_2014
--room K3401 7847 --force
Next: 5 Postgres for Application Developers
show more...
Marks
Author(s):
Craig Kerstiens
Location
K.3.401
Date
feb Sat 01
Days Raw Files
Start
14:00
First Raw Start
13:48
Duration
00:50:00
Offset
0:11:29
End
14:50
Last Raw End
14:59
Chapters
00:00
0:37:20
Total cuts_time
59 min.
https://fosdem.org/2014/schedule/event/postgres_performance_for_humans/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Postgres_Performance_for_Humans.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
<p>To many developers the database is a black box. You expect to be able to put data into your database, have it to stay there, and get it out when you query it... hopefully in a performant manner. When its not performant enough the two options are usually add some indices or throw some hardware at it. We'll walk through a bit of a clearer guide of how you can understand how database is doing from a 30,000 foot perspective as well as analyze specific problematic queries and how to tune them. In particular we'll cover:</p> <ul> <li>Postgres Caching</li> <li>Postgres Indexing</li> <li>Explain Plans</li> <li>Extensions</li> <li>More</li> </ul>
Comment:
production notes
2014-02-01/12_48_31.dv
Apply:
13:48:31 - 14:00:08 ( 00:11:37 )
S:
13:48:31 -
E:
14:00:08
D:
00:11:37
show more...
vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/K3401/2014-02-01/12_48_31.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
13:48:31
seconds: 0.0
Wall: 13:48:31
Duration
00:11:37
14:00:08
seconds: 0.0
Wall: 13:48:31
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2014-02-01/13_00_09.dv
Apply:
14:00:09 - 14:37:29 ( 00:37:20 )
S:
14:00:09 -
E:
14:37:29
D:
00:37:20
show more...
vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/K3401/2014-02-01/13_00_09.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:00:09
seconds: 0.0
Wall: 14:00:09
Duration
00:37:20
14:37:29
seconds: 0.0
Wall: 14:00:09
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2014-02-01/13_37_30.dv
Apply:
14:37:30 - 14:59:27 ( 00:21:57 )
S:
14:37:30 -
E:
14:59:27
D:
00:21:57
show more...
vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/K3401/2014-02-01/13_37_30.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:37:30
seconds: 0.0
Wall: 14:37:30
Duration
00:21:57
14:59:27
seconds: 0.0
Wall: 14:37:30
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2014-02-01/12_48_31.dv
2014-02-01/13_00_09.dv
2014-02-01/13_37_30.dv
Veyepar
Video Eyeball Processor and Review
