Submit at most 1 time a day
-
WEEKLY CHALLENGE #2
- challenge
- 37 150
- The complexity of the algorithm is not always fixed. When the data changes, the complexity of the same algorithm will change. This challenge is a typical example. Please optimize memory and speed to compete with other programmers.
Ranking
-
NoUser nameLanguagePointRunning time (s)
-
1C++150 ( 1 tries)0.37
-
2C++150 ( 1 tries)0.45
-
3C++150 ( 1 tries)0.49
-
4C++150 ( 1 tries)0.51
-
5C++150 ( 1 tries)0.55
-
6C++150 ( 1 tries)0.64
-
7C++150 ( 1 tries)0.64
-
8Java150 ( 1 tries)0.8
-
9C++150 ( 1 tries)0.88
-
10Java150 ( 1 tries)0.88
Other Challenges
-
CHALLENGE #17: Finding the best algorithm - Competing other programers
-
dolv -
Zero -
CWJ_tourguide
- Challenge
- 137
- 24
- 100
-
CHALLENGE #16: Finding the best algorithm - Competing other programers
-
Zero
-
nhok2k9 -
kuroky2k
- challenge
- 68
- 6
- 100
-
CHALLENGE #15: Finding the best algorithm - Competing other programers
-
nguoilukhach97 -
Nhatbattu
-
[email protected]
- Challenge
- 128
- 18
- 100
-
CHALLENGE #14: Finding the best algorithm - Competing other programers
-
hello5423 -
dolv
-
[email protected]
- challenge
- 80
- 8
- 100
-
CHALLENGE #13: Finding the best algorithm - Competing other programers
-
[email protected] -
LeDucThinh_FPT_HCM -
[email protected]
- Algorithm
- Segment-tree
- challenge
- 96
- 5
- 100
-
CHALLENGE #12: Finding the best algorithm - Competing other programers
-
LeDucThinh_FPT_HCM
-
[email protected]
-
Zero
- binary search
- sort
- challenge
- 90
- 1
- 140
-
CHALLENGE #11: Finding the best algorithm - Competing other programers
-
AnhDQ14 -
Zero
-
[email protected]
- trie
- string
- challenge
- 147
- 23
- 100
-
CHALLENGE #10: Finding the best algorithm - Competing other programers
-
nghethuat102
-
dolv
-
Zero
- ct
- trie
- STL
- challenge
- 88
- 15
- 100